document hackage archive format #749

Open
bos opened this Issue May 24, 2012 · 1 comment

Projects

None yet

1 participant

@bos
Contributor
bos commented May 24, 2012

(Imported from Trac #759, reported by claus on 2010-11-04)

I often find myself writing example code that I'd like to distribute via cabal, but without further burdening hackage with not generally useful packages.

The source code has an undocumented(?) option --remote-repo that seems to serve that purpose, but there is little documentation, sometimes conflicting info, about how to put this to use.

Mailing list threads:

[http://www.haskell.org/pipermail/haskell-cafe/2010-November/085860.html](http://www.haskell.org/pipermail/haskell-cafe/2010-November/085860.html)
[http://www.haskell.org/pipermail/haskell-cafe/2010-November/085900.html](http://www.haskell.org/pipermail/haskell-cafe/2010-November/085900.html)

Repo layout descriptions (differs between hackage 1.0 and 2.0, which is hardcoded in cabal-install):

[http://hackage.haskell.org/trac/hackage/wiki/HackageDB](http://hackage.haskell.org/trac/hackage/wiki/HackageDB)
[http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/URIs](http://hackage.haskell.org/trac/hackage/wiki/HackageDB/2.0/URIs)

Related tickets: #758, comment:6🎫428

@bos
Contributor
bos commented May 24, 2012

(Imported comment by @dcoutts on 2010-11-04)

I think the better solution for this use case is ticket #524 which is about making this possible:

cabal install http://code.haskell.org/~user/foo/foo-0.9.tar.gz
The problem with --remote-repo for this use case is that it creates a persistent local cache, which is not what you would want for a one-off command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment