Hi, Am Montag, den 21.04.2014, 11:38 +0200 schrieb Magnus Therning:
Then I have to say it is rather irritating that there is no way for me to safely provide the latest version of cabal-install!
the same problem affects Debian, and I find it equally irritating. Not sure how Fedora handles this – Jens, did you find a problem around this? One possibility would be to manually bundle the Cabal and cabal-install sources into one (dpkg supports source packages with multiple original tarballs), build the new Cabal just to be used to build cabal-install and link that statically (which is the default). This would provide an up-to-date cabal-install binary without having to ship a new Cabal version as a library. Or does cabal-install require the matching version of Cabal to be registered to work? Alternatively it might be possible to build ghc with a newer Cabal. Not sure what that might break. I believe there was talk to avoid having ghc depend on Cabal (it uses very little of it anyways), and indeed, there is https://ghc.haskell.org/trac/ghc/ticket/8244 but work got stalled 7 months ago. Fixing tht would solve the problems for us distributions – maybe someone wants to pick up the work? Greetings, Joachim PS: https://ghc.haskell.org/trac/ghc/ticket/8947 is a related bug (though about ghc’s dependency on binary, not on Cabal). -- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org