How to Install and Uninstall ghc-ghc-byteorder Package on openSuSE Tumbleweed

Last updated: May 29,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "ghc-ghc-byteorder" package

Please follow the guidance below to install ghc-ghc-byteorder on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                ghc-ghc-byteorder
            
                    
    
    Copied

2. Uninstall "ghc-ghc-byteorder" package

In this section, we are going to explain the necessary steps to uninstall ghc-ghc-byteorder on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                ghc-ghc-byteorder
            
                    
    
    Copied

3. Information about the ghc-ghc-byteorder package on openSuSE Tumbleweed

Information for package ghc-ghc-byteorder:
------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ghc-ghc-byteorder
Version : 4.11.0.0.10-4.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 1,5 KiB
Installed : No
Status : not installed
Source package : ghc-ghc-byteorder-4.11.0.0.10-4.1.src
Summary : "GHC.ByteOrder" API Compatibility Layer
Description :
This package transparently supplies the "GHC.ByteOrder" API as provided in
'base-4.11.0.0' for legacy GHC releases which didn't provide it yet (i.e.
GHC 7.0 through GHC 8.2).
This release reexports [GHC.ByteOrder from
base](https://hackage.haskell.org/package/base-4.11.1.0/docs/GHC-ByteOrder.html)
via Cabal's 'reexported-modules' mechanism. For GHC 8.2 and earlier a different
release of 'ghc-byteorder' (with the same minor version) is eligible by the
Cabal solver with a backported "GHC.ByteOrder" module.
In order to use this compatibility layer, simply declare a dependency on
'ghc-byteorder' in your '.cabal' package description like so
> build-depends: ghc-byteorder ^>= 4.11.0.0
And your code will be able to access this respective API version of the module
via the usual
> import GHC.ByteOrder
mechanism.