cabal-install version on hackage
Hello all, This is actually a question about hackage, but looks like there's no separate hackage mailing list. I'm suffering from the issue reported in here: http://hackage.haskell.org/trac/hackage/ticket/656. In brief, cabal had a bug that prevented it from running haddock successfully if a package contained both a library and an executable that depended on it. The good news is that the bug has been fixed, about 5 months ago in fact. Unfortunately, it looks like there hasn't been an official cabal-install release since. In any case, the version of cabal that hackage uses certainly does not have this fix included, hence packages that contain library+executable combos in the newer style fail to build on the hackage site. Is there a known workaround to this problem, short of dropping the "self" dependency in the cabal file? Would it be too much to ask if hackage can upgrade it's cabal? Would that break further things? Thanks, -Levent.
On Wed, Dec 21, 2011 at 05:34:33AM +0000, Levent Erkok wrote:
I'm suffering from the issue reported in here: http://hackage.haskell.org/trac/hackage/ticket/656. In brief, cabal had a bug that prevented it from running haddock successfully if a package contained both a library and an executable that depended on it. The good news is that the bug has been fixed, about 5 months ago in fact. Unfortunately, it looks like there hasn't been an official cabal-install release since. In any case, the version of cabal that hackage uses certainly does not have this fix included, hence packages that contain library+executable combos in the newer style fail to build on the hackage site.
Is there a known workaround to this problem, short of dropping the "self" dependency in the cabal file? Would it be too much to ask if hackage can upgrade it's cabal? Would that break further things?
Using a development version of cabal-install would run the risk of breaking other packages. A release that contains this fix would be better.
Is there a known workaround to this problem, short of dropping the "self" dependency in the cabal file? Would it be too much to ask if hackage can upgrade it's cabal? Would that break further things?
Using a development version of cabal-install would run the risk of breaking other packages. A release that contains this fix would be better.
Agreed. I couldn't find anything specific about the release plans on the cabal web site (http://www.haskell.org/cabal/), so I've filed a ticket (http://hackage.haskell.org/trac/hackage/ticket/907) to have discussion on whether it's time for a new release. End of the year is a busy time for everyone, but a new cabal-install release will be a nice new-year gift to the community if the lead developers can squeeze it in. -Levent.
participants (2)
-
Levent Erkok -
Ross Paterson