Packaging:Haskell

= Haskell Packaging Guidelines = This documents the guidelines and conventions for packaging Haskell projects in Fedora.

What is Haskell?
"Haskell is an advanced purely functional programming language. The product of more than twenty years of cutting edge research, it allows rapid development of robust, concise, correct software. With strong support for integration with other languages, built-in concurrency, debuggers, profilers, rich libraries and an active community, Haskell makes it easier to produce flexible, maintainable high-quality software." -- (from http://haskell.org/)

GHC
GHC, the Glasgow Haskell Compiler, is the most popular and widely used Haskell compiler. It complies with Haskell 98, the latest official language specification, and also includes various experimental language ideas. It represents a good picture of what the future of Haskell will look like, so it is a good choice for development. Most Haskell programs work better or only with GHC. So currently these guidelines mostly focus on packaging for GHC. At some later stage if the need arises they may be extended to cover other implementations in more detail.

Packages should normally be compiled with GHC where possible. Some Haskell packages might require some other compiler extension not available in GHC but in another compiler implementation in which case that compiler would have to be included in Fedora first before the package can get added to Fedora. If a package needs special language features they should be mentioned in the review and documented in comments in the spec file.

''Rationale: GHC is the best supported compiler in Fedora currently. Therefore, if something goes wrong, we have a larger skill base to ask for help.''

Cabal
"Cabal is a system for building and packaging Haskell libraries and programs. It defines a common interface for package authors and distributors to easily build their applications in a portable way. Cabal is part of a larger infrastructure for distributing, organizing, and cataloging Haskell libraries and programs.

''Specifically, the Cabal describes what a Haskell package is, how these packages interact with the language, and what Haskell implementations must do to support packages. The Cabal also specifies some infrastructure (code) that makes it easy for tool authors to build and distribute conforming packages.''

''The Cabal is only one contribution to the larger goal. In particular, the Cabal says nothing about more global issues such as how authors decide where in the module name space their library should live; how users can find a package they want; how orphan packages find new owners; and so on."''

(from http://haskell.org/cabal)

Summary and Description
When packaging things out of Hackage or other sources, you may find that the summary or description is incomplete or lacks detail. Please try to include an appropriate summary and adequate description for Fedora of the library or program in the package so users will know what it does.

Build and Install
and  can be done through a series of macros that ensure correctness.

%build %cabal_configure --ghc -p %cabal build %cabal haddock

configures the package for building with ghc and profiling. Note: library packages should include profiling libraries where possible or include a justification for not doing so. If you omit profiling libraries (the   option above), anyone wanting to install a profiling version of a dependent library or application will be unable to do so, which is generally considered bad form. There is no need to provide profiling for non-library packages.

will build a package without installing it.

builds HTML Haddock documentation files.

%install rm -rf ${RPM_BUILD_ROOT} %cabal_install

will install the package without including the registration scripts for ghc's library management. For libraries there are additional macros for generating the install scripts and filelists: see below.

Naming
The names of Haskell library packages should be prefixed with the compiler or interpreter they are intended for. Package names should follow the upstream naming and preserve case. For example, the   library from Hackage packaged for GHC would be named   in Fedora, and the   library would be named.

If a library is packaged for more than one Haskell compiler or interpreter, the base name should instead be prefixed with, e.g.  .  Such a package would then have subpackages for each compiler and/or interpreter it is built for (e.g.  ,  , etc.

''Rationale: The Fedora Project tries to follow upstream as closely as possible. Haskell upstream packages maintain consistent naming schemes across tarball, cabal and ghc package names, and mixed case names are tracked well.''

Static vs. Dynamic Linking
Current releases of GHC do not yet support generating shared libraries, so all ghc libraries are static and library packages of them should provide themselves as a -devel package also to allow migrating parts of them to -devel subpackages in the future when shared libraries become the norm:

Provides: ghc-%{pkg_name}-devel = %{version}-%{release}

Static linking means that when updating any library, all packages that depend on it will also need to be rebuilt before they see any changes, and in the event of a security advisory, all of them need to be rebuilt also.

This is not true for linking to other languages using the Foreign Function Interface (FFI). When linking to these libraries, the standard dynamic linker is used.

Note: the situation is similar to OCaml, and the usual rules that apply there apply here as well.

Keep in mind though, that some special packages may still do code generation at runtime in which case they may need Requires as well as BuildRequires for their dependencies: examples include xmonad and yi which may require certain libraries to be present to work.

Package directory
GHC libraries should be installed under  as done by Cabal.

%global pkg_libdir %{_libdir}/ghc-%{ghc_version}/%{pkg_name}-%{version}

File lists
You can generate filelists for libraries and profiling library subpackages using the following macro, rather than doing it by hand:

%ghc_gen_filelists %{name}

This macro takes one parameter, which is just a name prefix to be used for the file lists. This same parameter must be used later in the files section.

The files section would then look something like this:

%files -f %{name}.files %doc LICENSE README %{pkg_docdir}

%files -n %{name}-prof -f %{name}-prof.files

Install scripts
Libraries must be registered with the installed ghc package.

To generate registration scripts that can be embedded in the package first include the following in %build: %ghc_gen_scripts and then in %install install them with: %ghc_install_scripts

Finally the actual registering of packages must be done at install and uninstall time with the following scriplets: %post -n ghc-%{pkg_name} %ghc_register_pkg

%preun -n ghc-%{pkg_name} if [ "$1" -eq 0 ] ; then %ghc_unregister_pkg fi

Documentation
Normal doc files for a package should live in the usual place. Haskell supports inline API docs using the  tool (bundled in the   package as of 6.10), for which the situation is somewhat different. The master directory for Haddock files is, with one directory per package under there. The  file for this directory should be regenerated every time a package is installed, upgraded, or removed. Since  is owned by   it is recommended to subpackage haddock documentation in a   subpackage, which can require.

If a package comes with meaningful Haddock documentation, your spec file should define

%global pkg_docdir %{_docdir}/ghc/libraries/%{pkg_name}

and the  section should contain the following:

%cabal haddock

This will cause the HTML version of the Haddock documentation to be generated. If built, it will automatically be installed to the correct location by  without any further intervention.

To automatically update the master index of all Haddock documentation in, add the following to your   and   scriptlets:

%post %ghc_reindex_haddock

%postun if [ "$1" -eq 0 ] ; then %ghc_reindex_haddock fi

The ghc haddock docs index will then be updated after installation, update, or removal of the package.

Finally, you'll want to add the following to your  section, so that the Haddock docs will be picked up correctly.

%{pkg_docdir}

Naming
For packages of Haskell programs the usual Fedora Package Naming Guidelines must be followed: ie in they should follow the upstream name. Examples include projects like,  , and. If the package also generates libraries, then the libraries SHOULD be subpackaged as a Haskell library package named after the compiler or interpreter as above.

Any libraries provided should go into a separate subpackage: eg the spec file for xmonad would generate three rpm packages:,  , and. xmonad would require, but not visa versa. would contain a line in its description explaining that these are the libraries necessary for  to run.

''Rationale: Program packages should be easy to find by their upstream name. Binaries are recognized on their name alone. Furthermore, they generally do not require a compiler to run. Therefore the name provided should simply be the upstream name.

Debug Information
Debuginfo packages should not be built for GHC binaries, since they will be empty anyway.

%global debug_package %{nil}

Rationale: GHC does not emit DWARF debug data.

Macros
A number of macros are defined for convenince for packaging cabal packages and libraries for ghc. Similar macros could also be defined for other compilers. It would be good to follow this scheme as far as possible also when implementing macros for other Haskell compilers or interpreters to keep portability.


 * %cabal
 * %cabal_configure
 * %cabal_makefile
 * %ghc_gen_scripts
 * %cabal_install
 * %ghc_install_scripts
 * %ghc_gen_filelists
 * %ghc_register_pkg
 * %ghc_unregister_pkg
 * %ghc_reindex_haddock

You can find the current definitions in the ghc package.

Spec Templates
There are three types of packages: Library only, Library and Binary, and Binary only. Templates are provided for all three cases since they are slightly different:


 * Library Only Template
 * Binary Only Template
 * Library and Binary Template.

provides a simple script which can generate .spec files using these templates directly out of a Cabal package or .cabal file for any of the three cases. The .spec files should build for most general Cabal hackage packages with minimal changes: for example you might need to specify BuildRequires for other build dependencies and possibly Requires for any runtime or linking dependencies. Please report any problems in bugzilla (in the cabal2spec component of the Fedora product).