How to Install and Uninstall ghc-base-noprelude Package on openSuSE Tumbleweed

Last updated: May 18,2024

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

1. Install "ghc-base-noprelude" package

Please follow the step by step instructions below to install ghc-base-noprelude on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                ghc-base-noprelude
            
                    
    
    Copied

2. Uninstall "ghc-base-noprelude" package

Please follow the instructions below to uninstall ghc-base-noprelude on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                ghc-base-noprelude
            
                    
    
    Copied

3. Information about the ghc-base-noprelude package on openSuSE Tumbleweed

Information for package ghc-base-noprelude:
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ghc-base-noprelude
Version : 4.13.0.0-4.10
Arch : x86_64
Vendor : openSUSE
Installed Size : 1,5 KiB
Installed : No
Status : not installed
Source package : ghc-base-noprelude-4.13.0.0-4.10.src
Summary : "base" package sans "Prelude" module
Description :
This package simplifies defining custom "Prelude"s without having to use
'-XNoImplicitPrelude' by re-exporting the full module-hierarchy of the
[base-4.13.0.0](https://hackage.haskell.org/package/base-4.13.0.0) package
/except/ for the "Prelude" module.
An usage example for such a "Prelude"-replacement is available with the
[Prelude](http://hackage.haskell.org/package/Prelude) package.
Starting with GHC 7.10 & Cabal-1.22 this package makes use of the package-level
'reexported-modules' feature.
Each version of 'base-noprelude' depends on a specific 'base'-version and thus
mirrors 'base''s versioning (with the exception that 'base-noprelude' needs to
add an /additional/ 5th version component in case of bug-fix releases).
See for more information.