On Sun, Jan 2, 2011 at 12:20, Peter Simons
Hi Magnus,
>> the gist of this issue is that "parsec >= 3.0 || == 2.1.*" is translated to >> "parsec>=3.0", which is just plain wrong. Now, wouldn't it be easiest to >> modify cabal2arch so that it translates that specification to "parsec>=2.1"? >> A straight-forward algorithm to accomplish that would be to use the *lowest* >> version bound in these kinds of alternatives. Right now, cabal2arch appears >> to be using the *first* version bound, which is not exactly optimal. > > Well, there's an obvious problem with what you suggest, since > "parsec>=2.1" is plain wrong too!
why is that?
Now you make me think that I might have missed something, but surely parsec version 2.2 wouldn't satisfy the former, but would satisfy the latter. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus