Difference between revisions of "Haskell package guidelines"

From ArchWiki
Jump to: navigation, search
m (Bot: Removing from Category:Guidelines (English))
(→‎Haskell packages)
(47 intermediate revisions by 17 users not shown)
Line 1: Line 1:
−
[[Category:Package development (English)]]
+
[[Category:Package development]]
 +
[[it:Haskell Package Guidelines]]
 +
{{Package Guidelines}}
  
−
{{i18n|Haskell package guidelines}}
+
[[Wikipedia:Haskell_(programming_language)|Haskell]] is well supported on Arch Linux.
 +
GHC and a few core packages are available in the [[Official Repositories|official repositories]].
 +
For more serious Haskellers, the [[ArchHaskell]] community project provides many packages from [http://hackage.haskell.org Hackage], and the number is growing.
  
−
'''Haskell on Arch Linux'''
+
See the [[ArchHaskell]] community page for contact details and ways to help.
  
−
Haskell is well supported on Arch Linux, with GHC and other key tools available via pacman, a growing number of packages made available by the ArchHaskell group, and a large part of [http://hackage.haskell.org hackage.haskell.org] library database [http://aur.archlinux.org/packages.php?O=0&L=0&C=0&K=arch-haskell&SeB=m&SB=n&SO=a&PP=100&do_Search=Go available via AUR].
+
== Haskell packages ==
 +
To use Haskell on Arch Linux, you have two mutually exclusive options:
 +
# Use packages from the official Arch Linux repositories. These are a well maintained small subset of all Haskell packages. Just install them the way you would install anything else on Arch Linux. Examples of what is available: in the [https://www.archlinux.org/packages/?arch=x86_64&repo=Extra&q=haskell&last_update=&limit=50 extra] and [https://www.archlinux.org/packages/?arch=x86_64&repo=Community&q=haskell&last_update=&limit=50 community] repositories. The packages here should satisfy people who just want to use the Haskell Platform. You may also combine this option with other packages from unofficial sources like the AUR.
 +
# Use the ArchHaskell project's unofficial repositories. These contain a much larger subset of what's available on Hackage. As a community effort, we often need volunteers to help maintain and add more packages to these repositories. Read on for information about using them. A note for [[xmonad]] users: if you switch to this option, you need to install the '''haskell-xmonad''' package instead of {{Pkg|xmonad}} (which is in the official community repo and has different dependencies).
  
−
The community around Haskell on Arch is active and well organized but your help is always welcome.
+
=== [haskell-core] ===
 +
The [haskell-core] repository is the base repository of packages maintained by the ArchHaskell team.
 +
[haskell-core] can be accessed by adding the following entry to {{ic|/etc/pacman.conf}} (above [extra]):
  
−
== Community ==
+
[haskell-core]
 +
Server = http://xsounds.org/~haskell/core/$arch
  
−
All the details on the [[ArchHaskell]] group is available on its own page.
+
or
  
−
== Haskell Packages ==
+
[haskell-core]
 +
Server = http://www.kiwilight.com/haskell/core/$arch
  
−
The core Haskell tools are available in the core system (extra):
+
The set of packages in the [haskell-core] repository is derived from the '''habs''' tree officially located [https://github.com/archhaskell/habs here]. A tool called [https://github.com/magthe/cblrepo cblrepo] is used to keep the '''habs''' tree synchronized with the official Haskell packages from [http://hackage.haskell.org/packages/hackage.html Hackage].
  
−
==== <nowiki>[Extra]</nowiki> ====
+
Putting [haskell-core] above [extra] will ensure that the packages from [haskell-core] take precedence, in case of duplicate packages in the two repositories.
  
−
* [http://www.archlinux.org/packages/?arch=x86_64&repo=Extra&q=haskell&last_update=&limit=50 Haskell packages in the core system]
+
The repositories provide both file listings (by using {{ic|repo-add --files}}), package deltas ({{ic|repo-add --delta}}), and both packages and the database are signed.  The fingerprint of the key used for signing is:
  
−
Our policy is for [extra] to provide the Haskell platform, and popular Haskell applications.
+
  pub  2048D/4209170B 2012-12-26
 +
        Key fingerprint = F310 4992 EBF2 4EB8 72B9  7B9C 32B0 B453 4209 170B
 +
  uid                  ArchHaskell (Magnus Therning) <magnus@therning.org>
 +
  sub  2048D/A418C0FE 2012-12-26
  
−
==== <nowiki>[haskell]</nowiki> ====
+
If you use {{ic|SigLevel &#61; Required TrustedOnly}} in {{ic|/etc/pacman.conf}} for [haskell-core], then you need to do the following to add Magnus Therning's key:
 +
  # sudo pacman-key -r 4209170B
 +
  # sudo pacman-key --lsign-key 4209170B
  
−
The packages maintained by the ArchHaskell group can be accessed by adding the following entry to pacman.conf:
+
Force a refresh of all package lists:
 +
  # sudo pacman -Syy
  
−
[haskell]
+
=== [haskell-happstack] ===
−
Server = http://andromeda.kiwilight.com/$repo/$arch
+
The [haskell-happstack] repository contains packages for web development based on the [http://happstack.com/ Happstack] framework. It requires [[Haskell_Package_Guidelines#.5Bhaskell-core.5D|[haskell-core]]], and includes most of the Happstack packages in [http://hackage.haskell.org/ HackageDB], plus [http://gitit.net/ Gitit] and [http://clckwrks.com/ clckwrks], all their dependencies not in [haskell-core] and some other not web related packages. To enable the repository, add the following entry to {{ic|/etc/pacman.conf}}:
  
−
==== <nowiki>AUR</nowiki> ====
+
  [haskell-happstack]
 +
  Server = ftp://noaxiom.org/$repo/$arch
  
−
* [http://aur.archlinux.org/packages.php?O=0&L=0&C=0&K=arch-haskell&SeB=m&SB=n&SO=a&PP=100&do_Search=Go Haskell packages in AUR]
+
Add and sign the maintainer's key:
  
−
A huge number (almost 2000) packages built from http://hackage.haskell.org
+
  # pacman-key -r B0544167
 +
  # pacman-key --lsign-key B0544167
  
−
These generally improve on installing directly from Hackage as they resolve required C libraries. They can be installed as, for example:
+
Bug reports and feature requests in [https://github.com/tensor5/haskell-happstack/issues GitHub].
  
−
    sudo paktahn -S haskell-csv
+
=== [haskell-web] ===
 +
The [haskell-web] repository is not maintained anymore. If you wish to help, please send a mail to the list or use the IRC channel.
 +
The repository was built on [haskell-core], providing several more packages, especially those useful for web applications.
  
−
Anything not found here can be installed via [http://aur.archlinux.org/packages.php?ID=17411 cabal-install] direct from Hackage.
+
[haskell-web]
 +
Server = http://archhaskell.mynerdside.com/$repo/$arch
  
−
== Guidelines ==
+
=== Last resorts ===
 +
* [https://aur.archlinux.org/packages.php?O=0&K=haskell- Haskell packages in the AUR]
 +
* cabal-install directly
  
−
In almost all cases cabalised Haskell packages can be automatically translated into Arch packages, via the cabal2arch tool. It is strongly recommended that you use the latest released version of this tool, as it implements the packaging policy for Haskell packages. You can get it in several ways:
+
Unfortunately, many of the packages in the AUR are outdated due to a lack of resources.
 +
If you have the time, it is recommended to use cblrepo and create something like [haskell-web], which can then be added to the collection of haskell-providing repositories.
  
−
* Add the <nowiki>[haskell]</nowiki> repository to pacman.conf and use pacman do install the latest release.
+
=== Tips ===
−
* Download and build the [http://aur.archlinux.org/packages.php?ID=17471 source from AUR], either manually or using one of the many [[AUR Helpers]].
+
−
* Install directly from Hackage using "cabal install cabal2arch".
+
  
−
===cabal2arch: an example===
+
==== Haskell-Platform ====
 +
The haskell platform is a stabalised package set, and is in writing moment not available in the repos.
 +
A close equal would be to install GHC, cabal-install, haddock, happy and alex. So with [haskell-core] you would do "pacman -S ghc cabal-install haskell-haddock happy alex"
  
−
This example illustrates how to create a new package with cabal2arch. We'll make a new package for the delimited continuations library, CC-delcont:
+
Note: for official repos only, install "haddock" instead of "haskell-haddock"
  
−
First, set the name and email address to be used in the generated PKGBUILD:
+
== Improving ArchHaskell ==
  
−
export ARCH_HASKELL='My Name <my.name@domain.org>'
+
=== Community ===
 +
See the [[ArchHaskell]] community page and get in touch via the mailing list or the IRC channel.
  
−
Second, find [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/CC-delcont the hackage page for CC-delcont], then identify the link to the .cabal file. Use this link as an argument to cabal2arch:
+
=== Overview ===
 +
The plan is to have one user-facing repository, [haskell], which merges the packages available in various satellite repositories (like [haskell-web]), thereby distributing the maintenance load.
 +
One satellite repo is special, the [haskell-core] repository, which provides packages that are dependencies of all the other satellites.
  
−
<pre>
+
=== [haskell-core] maintenance ===
−
% cd /tmp
+
Ensure:
−
% cabal2arch http://hackage.haskell.org/packages/archive/pandoc/1.6.0.1/pandoc.cabal
+
* [haskell-core] is an Arch repo hosted at kiwilight and xsounds.
−
Using /tmp/tmp.D7HAJJx2js/pandoc.cabal
+
* [haskell-core] is in sync with the [https://github.com/archhaskell/habs habs] cblrepo database.
−
Feeding the PKGBUILD to `makepkg -g`...
+
−
==> Retrieving Sources...
+
−
  -> Downloading pandoc-1.6.0.1.tar.gz...
+
−
--2011-05-14 07:25:39--  http://hackage.haskell.org/packages/archive/pandoc/1.6.0.1/pandoc-1.6.0.1.tar.gz
+
−
Resolving hackage.haskell.org... 69.30.63.204
+
−
Connecting to hackage.haskell.org|69.30.63.204|:80... connected.
+
−
HTTP request sent, awaiting response... 200 OK
+
−
Length: 355477 (347K) [application/x-tar]
+
−
Saving to: “pandoc-1.6.0.1.tar.gz.part”
+
  
−
    0K .......... .......... .......... .......... .......... 14%  210K 1s
+
=== Other repo maintenance ===
−
    50K .......... .......... .......... .......... .......... 28%  393K 1s
+
For example, for haskell-foo, ensure:
−
  100K .......... .......... .......... .......... .......... 43%  338K 1s
+
* haskell-foo is a cblrepo database, possibly using packages from [haskell-core] as DistroPkgs.
−
  150K .......... .......... .......... .......... .......... 57%  419K 0s
+
* Whenever [haskell-core] is updated, haskell-foo's database is updated to match within a reasonable time.
−
  200K .......... .......... .......... .......... .......... 72%  404K 0s
+
−
  250K .......... .......... .......... .......... .......... 86%  554K 0s
+
−
  300K .......... .......... .......... .......... .......  100%  506K=0.9s
+
  
−
2011-05-14 07:25:40 (369 KB/s) - “pandoc-1.6.0.1.tar.gz.part” saved [355477/355477]
+
=== Creating another repo ===
  
−
==> Generating checksums for source files...
+
=== List of satellite repos ===
−
</pre>
+
−
 
+
−
Checking what was created:
+
−
 
+
−
% ls
+
−
haskell-pandoc
+
−
% cd haskell-pandoc
+
−
% ls
+
−
haskell-pandoc.install PKGBUILD
+
−
 
+
−
You can now inspect the PKGBUILD and install script for the library:
+
−
 
+
−
<pre>
+
−
# Maintainer:
+
−
_hkgname=pandoc
+
−
pkgname=haskell-pandoc
+
−
pkgver=1.6.0.1
+
−
pkgrel=1
+
−
pkgdesc="Conversion between markup formats"
+
−
url="http://hackage.haskell.org/package/${_hkgname}"
+
−
license=('GPL')
+
−
arch=('i686' 'x86_64')
+
−
makedepends=()
+
−
depends=('ghc' 'haskell-http=4000.1.1' 'haskell-bytestring=0.9.1.10' 'haskell-containers=0.4.0.0' 'haskell-directory=1.1.0.0' 'haskell-extensible-exceptions=0.1.1.2' 'haskell-filepath=1.2.0.0' 'haskell-mtl=2.0.1.0' 'haskell-network=2.3.0.2' 'haskell-old-time=1.0.0.6' 'haskell-parsec=3.1.1' 'haskell-pretty=1.0.1.2' 'haskell-process=1.0.1.5' 'haskell-random=1.0.0.3' 'haskell-syb=0.3' 'haskell-texmath<0.5' 'haskell-utf8-string>=0.3' 'haskell-xhtml=3000.2.0.1' 'haskell-xml<1.4' 'haskell-zip-archive<0.2')
+
−
options=('strip')
+
−
source=(http://hackage.haskell.org/packages/archive/${_hkgname}/${pkgver}/${_hkgname}-${pkgver}.tar.gz)
+
−
install=${pkgname}.install
+
−
md5sums=('d19a630462595941b3100dff6f839aa3')
+
−
build() {
+
−
    cd ${srcdir}/${_hkgname}-${pkgver}
+
−
    runhaskell Setup configure -O ${PKGBUILD_HASKELL_ENABLE_PROFILING:+-p } --enable-split-objs --enable-shared \
+
−
      --prefix=/usr --docdir=/usr/share/doc/${pkgname} --libsubdir=\$compiler/site-local/\$pkgid
+
−
    runhaskell Setup build
+
−
    runhaskell Setup haddock
+
−
    runhaskell Setup register  --gen-script
+
−
    runhaskell Setup unregister --gen-script
+
−
    sed -i -r -e "s|ghc-pkg.*unregister[^ ]* |&'--force' |" unregister.sh
+
−
}
+
−
package() {
+
−
    cd ${srcdir}/${_hkgname}-${pkgver}
+
−
    install -D -m744 register.sh  ${pkgdir}/usr/share/haskell/${pkgname}/register.sh
+
−
    install    -m744 unregister.sh ${pkgdir}/usr/share/haskell/${pkgname}/unregister.sh
+
−
    install -d -m755 ${pkgdir}/usr/share/doc/ghc/html/libraries
+
−
    ln -s /usr/share/doc/${pkgname}/html ${pkgdir}/usr/share/doc/ghc/html/libraries/${_hkgname}
+
−
    runhaskell Setup copy --destdir=${pkgdir}
+
−
}
+
−
</pre>
+
−
 
+
−
It follows the conventions for Haskell packages:
+
−
 
+
−
* Libraries are prefixed with "haskell-"
+
−
* All libraries that the package depend on are listed (libraries shipped with ghc are dealt with by having the ghc package provide them)
+
−
* It uses cabal to generate a post-install register/unregister script, with a standard name.
+
−
* We use haddock to build the documentation.
+
−
 
+
−
All Haskell libraries should follow these naming conventions, and using the latest release of cabal2arch will ensure this is the case.
+
−
 
+
−
NOTE: Beginning with cabal2arch 1.1-2, a new environment variable, '''PKGBUILD_HASKELL_ENABLE_PROFILING''', is generated into the PKGBUILD. If this variable is of non-zero length, such as "1" or "true", then profiling builds will occur. Thus, if a user desires profiling, then it is advised to export this environment variable in a file such as ~/.bashrc or ~/.zshrc.
+
−
 
+
−
===Guidelines for Libraries===
+
−
 
+
−
In general, each .cabal file should map to one PKGBUILD. The following conventions hold:
+
−
 
+
−
* libraries have their cabal names prefixed with "haskell-"
+
−
* all libraries have a dependency on 'ghc'
+
−
* all libraries that are depended on must be listed in the depends-array in the PKGBUILD
+
−
* be careful about dependencies from gtk2hs: cairo, svg, glib, gtk. These are all provided by the 'gtk2hs' package, not , e.g. "haskell-cairo"
+
−
 
+
−
Registering Haskell libraries is done via a register hook, see above.
+
−
 
+
−
===Guidelines for Programs ===
+
−
 
+
−
* Have their normal name. Examples: hmp3, xmonad, ghc, cabal-install
+
−
 
+
−
* Be careful about dynamically linked runtime dependencies on C. For example, all GHC-produced binaries have a runtime dependency on 'gmp'. OpenGL or GtT-based binaries will have additional 'depends'. cabal2arch will attempt to work out the C dependencies, but there may be others implied by Haskell dependencies that are missed.
+
−
 
+
−
* Use executable stripping, --enable-executable-stripping. cabal2arch will do this automatically.
+
−
 
+
−
== Automatic local building of Hackage Packages with cabal2arch using Bauerbill ==
+
−
{{Warning|''Bauerbill'' development has been officially discontinued: its latest version does not work with ''pacman>&#61;3.5''. See [https://bbs.archlinux.org/viewtopic.php?id&#61;115660].}}
+
−
Although there are a number of haskell packages on AUR, there will always be outdated packages on AUR. If this happens and you want to create a fully updated package you would normally use cabal2arch. This however can become painful/time consuming if you have numerous packages with different dependencies (some of which may/may not be updated). Instead you can automatic this process by using [[Bauerbill]] which has the --hackage flag, allowing you to create AUR packages from Hackage locally. Below is an example of some common commands
+
−
 
+
−
    bauerbill -S --hackage [pkgs] : build [pkgs] directly from Hackage*
+
−
    bauerbill -Si --hackage [pkgs] : look up information about [pkgs]
+
−
    bauerbill -Ss --hackage [args] : search for [args]
+
−
    bauerbill -Qu --hackage : list upgradable Hackage packages
+
−
 
+
−
Syncing packages with the --hackage flag will interactively download all dependencies of the package from Hackage, convert them using cabal2arch and then build/install them (while checking dependencies). You can combine this with the --aur flag to give precedence to Hackage packages that are on AUR
+

Revision as of 18:11, 18 December 2013

Template:Package Guidelines

Haskell is well supported on Arch Linux. GHC and a few core packages are available in the official repositories. For more serious Haskellers, the ArchHaskell community project provides many packages from Hackage, and the number is growing.

See the ArchHaskell community page for contact details and ways to help.

Haskell packages

To use Haskell on Arch Linux, you have two mutually exclusive options:

  1. Use packages from the official Arch Linux repositories. These are a well maintained small subset of all Haskell packages. Just install them the way you would install anything else on Arch Linux. Examples of what is available: in the extra and community repositories. The packages here should satisfy people who just want to use the Haskell Platform. You may also combine this option with other packages from unofficial sources like the AUR.
  2. Use the ArchHaskell project's unofficial repositories. These contain a much larger subset of what's available on Hackage. As a community effort, we often need volunteers to help maintain and add more packages to these repositories. Read on for information about using them. A note for xmonad users: if you switch to this option, you need to install the haskell-xmonad package instead of xmonad (which is in the official community repo and has different dependencies).

[haskell-core]

The [haskell-core] repository is the base repository of packages maintained by the ArchHaskell team. [haskell-core] can be accessed by adding the following entry to /etc/pacman.conf (above [extra]): 

[haskell-core]
Server = http://xsounds.org/~haskell/core/$arch

or 

[haskell-core]
Server = http://www.kiwilight.com/haskell/core/$arch

The set of packages in the [haskell-core] repository is derived from the habs tree officially located here. A tool called cblrepo is used to keep the habs tree synchronized with the official Haskell packages from Hackage.

Putting [haskell-core] above [extra] will ensure that the packages from [haskell-core] take precedence, in case of duplicate packages in the two repositories.

The repositories provide both file listings (by using repo-add --files), package deltas (repo-add --delta), and both packages and the database are signed. The fingerprint of the key used for signing is: 

 pub   2048D/4209170B 2012-12-26
       Key fingerprint = F310 4992 EBF2 4EB8 72B9  7B9C 32B0 B453 4209 170B
 uid                  ArchHaskell (Magnus Therning) <magnus@therning.org>
 sub   2048D/A418C0FE 2012-12-26

If you use SigLevel = Required TrustedOnly in /etc/pacman.conf for [haskell-core], then you need to do the following to add Magnus Therning's key: 

 # sudo pacman-key -r 4209170B
 # sudo pacman-key --lsign-key 4209170B

Force a refresh of all package lists: 

 # sudo pacman -Syy

[haskell-happstack]

The [haskell-happstack] repository contains packages for web development based on the Happstack framework. It requires [haskell-core], and includes most of the Happstack packages in HackageDB, plus Gitit and clckwrks, all their dependencies not in [haskell-core] and some other not web related packages. To enable the repository, add the following entry to /etc/pacman.conf: 

 [haskell-happstack]
 Server = ftp://noaxiom.org/$repo/$arch

Add and sign the maintainer's key: 

 # pacman-key -r B0544167
 # pacman-key --lsign-key B0544167

Bug reports and feature requests in GitHub.

[haskell-web]

The [haskell-web] repository is not maintained anymore. If you wish to help, please send a mail to the list or use the IRC channel. The repository was built on [haskell-core], providing several more packages, especially those useful for web applications. 

[haskell-web]
Server = http://archhaskell.mynerdside.com/$repo/$arch

Last resorts

Unfortunately, many of the packages in the AUR are outdated due to a lack of resources. If you have the time, it is recommended to use cblrepo and create something like [haskell-web], which can then be added to the collection of haskell-providing repositories.

Tips

Haskell-Platform

The haskell platform is a stabalised package set, and is in writing moment not available in the repos. A close equal would be to install GHC, cabal-install, haddock, happy and alex. So with [haskell-core] you would do "pacman -S ghc cabal-install haskell-haddock happy alex"

Note: for official repos only, install "haddock" instead of "haskell-haddock"

Improving ArchHaskell

Community

See the ArchHaskell community page and get in touch via the mailing list or the IRC channel.

Overview

The plan is to have one user-facing repository, [haskell], which merges the packages available in various satellite repositories (like [haskell-web]), thereby distributing the maintenance load. One satellite repo is special, the [haskell-core] repository, which provides packages that are dependencies of all the other satellites.

[haskell-core] maintenance

Ensure:

  • [haskell-core] is an Arch repo hosted at kiwilight and xsounds.
  • [haskell-core] is in sync with the habs cblrepo database.

Other repo maintenance

For example, for haskell-foo, ensure:

  • haskell-foo is a cblrepo database, possibly using packages from [haskell-core] as DistroPkgs.
  • Whenever [haskell-core] is updated, haskell-foo's database is updated to match within a reasonable time.

Creating another repo

List of satellite repos

Retrieved from "https://wiki.archlinux.org/index.php?title=Haskell_package_guidelines&oldid=289146"