How to Install and Uninstall wlcs.x86_64 Package on CentOS Stream 9

Last updated: October 06,2024

1. Install "wlcs.x86_64" package

In this section, we are going to explain the necessary steps to install wlcs.x86_64 on CentOS Stream 9


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                wlcs.x86_64
            
                    
    
    Copied

2. Uninstall "wlcs.x86_64" package

This is a short guide on how to uninstall wlcs.x86_64 on CentOS Stream 9:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                wlcs.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the wlcs.x86_64 package on CentOS Stream 9

Last metadata expiration check: 3:22:22 ago on Sat Mar 16 16:03:45 2024.
Available Packages
Name : wlcs
Version : 1.7.0
Release : 1.el9
Architecture : x86_64
Size : 7.6 M
Source : wlcs-1.7.0-1.el9.src.rpm
Repository : epel
Summary : Wayland Conformance Test Suite
URL : https://github.com/MirServer/wlcs
License : GPL-3.0-only AND (LGPL-2.0-only OR LGPL-3.0-only)
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.