How to Install and Uninstall wlcs.i686 Package on Fedora 34

Last updated: October 06,2024

1. Install "wlcs.i686" package

In this section, we are going to explain the necessary steps to install wlcs.i686 on Fedora 34


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                wlcs.i686
            
                    
    
    Copied

2. Uninstall "wlcs.i686" package

Here is a brief guide to show you how to uninstall wlcs.i686 on Fedora 34:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                wlcs.i686
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the wlcs.i686 package on Fedora 34

Last metadata expiration check: 2:58:20 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : wlcs
Version : 1.3.0
Release : 5.fc34
Architecture : i686
Size : 5.0 M
Source : wlcs-1.3.0-5.fc34.src.rpm
Repository : updates
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.