Difference between revisions of "Unofficial user repositories/ArchHaskell"

From ArchWiki
Jump to: navigation, search
(clean up)
(move "Improving ArchHaskell" section from Haskell Package Guidelines to ArchHaskell)
Line 20: Line 20:
 
* Magnus Therning
 
* Magnus Therning
 
* Leif Warner
 
* Leif Warner
 +
 +
 +
== 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 [https://github.com/archhaskell/habs 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 ===

Revision as of 04:25, 10 August 2014

The ArchHaskell group works on providing Haskell packages to the wider Arch Linux community. The goal is to provide all of Hackage as binary packages for easy installation.

See also Haskell package guidelines.

Resources

The main resources for the ArchHaskell community to interact and discuss are:

Membership

Membership is not required at all in order to contribute. Just fork the relevant repository, make some changes, and file a pull request.

There are currently two people with commit rights to the ArchHaskell repository at GitHub:

  • Magnus Therning
  • Leif Warner


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