Haskell is a general purpose, purely functional, programming language.
Haskell generates machine code that can be run natively on Linux. There is nothing special required to run a binary (already compiled) software, like the ones provided in the official repositories or by the ArchHaskell group. On the other side, AUR packages or source codes requires a compiler to build the software.
Installing the compiler alone permits to build Haskell source code. A few additional tools are needed for development work.
To build a Haskell source–code into native–code, a compiler must be installed. There are several implementations available, but the one used most (which is now de facto the reference) is the GHC (Glasgow Haskell Compiler). It is available in the official repositories as .
You can try it with the following file:
main = putStrLn "Hello, World"
and by running:
$ ghc Main.hs $ ./Main
Haskell development tools
To start developing in Haskell easily, one option is the haskell-platform bundle which is described as:
- The easiest way to get started with programming Haskell. It comes with all you need to get up and running. Think of it as "Haskell: batteries included".
- ghc ( ) — The compiler
- cabal-install ( ) — A command line interface for Cabal and Hackage
- haddock ( and ) — Tools for generating documentation
- happy ( ) — Parser generator
- alex ( ) — Lexical analyzer generator
Managing Haskell packages
Many Haskell libraries and executables are grouped in packages. They are all available on Hackage. To install and manage these packages, several methods are available and unusual ones are explained in the rest of this section.
The recommended workflow is the following:
- Official repositories or ArchHaskell repository as principal source of Haskell packages (the or is exclusive here)
- cabal-install (possibly with sandboxes) for Haskell development
- Arch User Repository for packages that are not available elsewhere
cblrepo is a tool used for maintaining Haskell packages for Linux distributions. A wrapper around this, AUR[broken link: archived in aur-mirror], can create PKGBUILD files from Hackage packages. See Haskell package guidelines for more information on creating new Haskell packages.
Pros/Cons of the different methods
The following table documents the advantages and disadvantages of different package management styles.
|Official repositories||Provided by ArchLinux developers, consistent versions of packages, already compiled||Only a few packages available|
|ArchHaskell repository||Provided by ArchHaskell group, consistent versions of packages, already compiled||Need manual intervention to get started with|
|cabal-install||All packages available||Installed in home folder, is not a package manager, incompatible versions of packages possible (aka. cabal hell)|
|Arch User Repository||Simple to get started||Risk of unmaintained or orphaned packages, incompatible versions of packages possible|
See ArchHaskell for details.
Preparation and $PATH
Install official repositories.from the
To run installed executables without specifying the path, the cabal binary folder
~/.cabal/bin must be added to the
$PATH variable. That can be done by putting the following line in your shell configuration file, for instance
~/.bashrc for or
~/.zshrc for :
PATH=$PATH:~/.cabal/binTo run executables within a cabal sandbox, you must also add
$ cabal update $ cabal install <pkg>
It is possible to install a package system–wide with the
--global flag, but this is strongly discouraged. With the user–wide install, all files are kept in
~/.cabal and libraries are registered to
~/.ghc, offering the possibility to do a clean-up easily by simply removing these folders. With system–wide install, the files will be dispersed in the file system and difficult to manage.
There is no easy way to do it.