On Tue, Dec 28, 2010 at 09:08, Rémy Oudompheng
Hello,
Since pacman's dependency specification is much less powerful than in Cabal, cabal2arch may output wrong version constraints while trying to approximate the true specified dependencies. I prefer this to dropping all version requirements when they cannot be expressed in the pacman's way.
This sounds reasonable. However, do you have examples of dependencies that CABAL can express but pacman can't? (I was under the impression that the difference was that CABAL allowed more terse expressions, not that it allowed more.)
In order to get improved PKGBUILDs I thought we could have a better usage of the dependency resolution capabilities in the Cabal library, this is summed up in this commit
http://github.com/remyoudompheng/archhaskell/commit/2e614b2
This adds an extra file, platform-provides.txt, that lists our preferred versions for various packages. For the moment I have filled it with the contents of Haskell Platform.
Is it worth considering downloading this file dynamically, rather than compiling it into the executable statically? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus