Difference between revisions of "Hackage"
Jump to navigation
Jump to search
m (format) |
DuncanCoutts (talk | contribs) (reorganise the page) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | '''Hackage''' is the Haskell community's central package archive. Package authors use it to publish their libraries and programs while other Haskell programmers use tools like [[cabal-install]] to download and install packages (or people get the packages via their distro). |
||
| − | '''Hackage''' is a community development project consisting of a number of components related to packaging Haskell software: |
||
| + | == Links == |
||
| − | * [[Cabal]] |
||
| − | * cabal-setup |
||
| − | * HackageDB |
||
| − | * cabal-install |
||
| − | + | * The main [https://hackage.haskell.org/ web interface]. It also has [https://hackage.haskell.org/api interfaces] used by tools like [[cabal-install]]. |
|
| + | * Hackage works with Haskell packages in the [[Cabal]] format. |
||
| + | * [http://status.haskell.org/ Server status] |
||
| + | * [https://github.com/haskell/hackage-server/wiki Hackage server wiki], about the code that runs the server. |
||
| + | == Getting help == |
||
| + | * For issues with accounts or permissions please contact the administrators by email [mailto:admin@hackage.haskell.org admin@hackage.haskell.org] |
||
| − | Hackage ideas posted to this wiki. New ideas are better submitted over the corresponding [http://hackage.haskell.org/trac/hackage project page]. |
||
| + | * Submit bug reports in [https://github.com/haskell/hackage-server/issues the github issue tracker]. |
||
| + | * New ideas are best submitted at the [https://github.com/haskell/hackage-server/issues?labels=enhancement&page=1&state=open project page]. |
||
| + | * There is a #hackage IRC channel on freenode for the discussion of the development of the hackage server and related tools such as Cabal/cabal-install. |
||
| + | |||
| + | == Administration and policies == |
||
| + | |||
| + | * [[Taking over a package]] on Hackage, with the assistance of the existing maintainer or otherwise |
||
| + | * [[Hackage trustees]]: what they do, who they are, what guidelines they follow. |
||
| + | |||
| + | == Related resources == |
||
| + | |||
| + | * There is a daily updated [[BibTeX]] database for [http://code.haskell.org/~thielema/bibtex/hackage.bib.gz citing] packages. |
||
| + | |||
| + | == Blog posts == |
||
| + | |||
| + | * [http://fuuzetsu.co.uk/blog/posts/2014-01-06-Fix-your-Hackage-documentation.html Fix your Hackage documentation] |
||
| + | * [http://fuuzetsu.co.uk/blog/posts/2014-01-06-Hackage-documentation-v2.html Hackage documentation v2] |
||
| − | Wanted features: |
||
| − | * Bug tracking |
||
| − | * Project info page (wiki-like?) |
||
| − | * Hosting of documentation. |
||
| − | Assumptions: |
||
| − | * Darcs is the one true revision control system. |
||
| − | * One darcs repo per package. |
||
[[Category:Packages]] |
[[Category:Packages]] |
||
Revision as of 01:16, 12 February 2015
Hackage is the Haskell community's central package archive. Package authors use it to publish their libraries and programs while other Haskell programmers use tools like cabal-install to download and install packages (or people get the packages via their distro).
Links
- The main web interface. It also has interfaces used by tools like cabal-install.
- Hackage works with Haskell packages in the Cabal format.
- Server status
- Hackage server wiki, about the code that runs the server.
Getting help
- For issues with accounts or permissions please contact the administrators by email admin@hackage.haskell.org
- Submit bug reports in the github issue tracker.
- New ideas are best submitted at the project page.
- There is a #hackage IRC channel on freenode for the discussion of the development of the hackage server and related tools such as Cabal/cabal-install.
Administration and policies
- Taking over a package on Hackage, with the assistance of the existing maintainer or otherwise
- Hackage trustees: what they do, who they are, what guidelines they follow.