How to Install and Uninstall wlcs.x86_64 Package on Fedora 36

Last updated: September 19,2024

1. Install "wlcs.x86_64" package

Please follow the steps below to install wlcs.x86_64 on Fedora 36


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                wlcs.x86_64
            
                    
    
    Copied

2. Uninstall "wlcs.x86_64" package

In this section, we are going to explain the necessary steps to uninstall wlcs.x86_64 on Fedora 36:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                wlcs.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the wlcs.x86_64 package on Fedora 36

Last metadata expiration check: 3:23:28 ago on Thu Sep 8 02:05:26 2022.
Available Packages
Name : wlcs
Version : 1.4.0
Release : 1.fc36
Architecture : x86_64
Size : 6.0 M
Source : wlcs-1.4.0-1.fc36.src.rpm
Repository : fedora
Summary : Wayland Conformance Test Suite
URL : https://github.com/MirServer/wlcs
License : GPLv3
Description : wlcs aspires to be a protocol-conformance-verifying test suite usable by
: Wayland compositor implementors.
:
: It is growing out of porting the existing Weston test suite to be run in Mir’s
: test suite, but it is designed to be usable by any compositor.
:
: wlcs relies on compositors providing an integration module, providing wlcs with
: API hooks to start a compositor, connect a client, move a window, and so on.
:
: This makes both writing and debugging tests easier - the tests are (generally)
: in the same address space as the compositor, so there is a consistent global
: clock available, it’s easier to poke around in compositor internals, and
: standard debugging tools can follow control flow from the test client to the
: compositor and back again.