Sun May 4 06:16:26 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Add PackageIndex.dependencyCycles
Finds any cycles (strongly connected components) in the dependencies
of set of packages. This is useful for checking the correctness of
installation plans.
M ./Distribution/Simple/Packag
Sun May 4 06:08:02 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Change dependencyInconsistencies to not take the pseudo top package
The one case where we need the pseudo top package we can use
PackageIndex.insert instead to get the same effect and there
are other cases in cabal-install wh
Sun May 4 06:03:17 PDT 2008 Duncan Coutts <[EMAIL PROTECTED]>
* Reverse the order of the args to PackageIndex.insert
To take the index last like the other functions and like Data.Map.
It is actually more convenient that way round.
M ./Distribution/Simple/PackageIndex.hs -2 +2
View pat
#232: implement extended syntax for package version ranges
+---
Reporter: duncan |Owner: nominolo
Type: enhancement| Status: new
Priority: normal |Milestone: Cabal-1.
Thomas Schilling wrote:
apfelmus wrote:
In both cases, the basic idea is that the library user should *not*
think about library versions, he just uses the one that is in
scope on his system.
I think we mean the same thing.
Yes, albeit with the small difference that in my case, the library
