#435: ban upwardly open version ranges in dependencies on base ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.8.3 | Platform: ----------------------------+----------------------------------------------- Comment (by ross@soi.city.ac.uk): Replying to [comment:4 duncan]:
Replying to [comment:3 ross]:
You will need to get GHC releases of core packages to follow the PVP strictly if you do this.
It'd certainly be much more consistent though I'm not sure it's strictly necessary. I mean, I don't think we need to wait. The sooner we get hackage to enforce this, the larger the set of packages that will move over smoothly when we get base 5.
OK, I missed that you were just talking about base (but base is still a problem).
We've been treating base as if it were just had one major version digit rather than the two specified by the PVP. Most packages follow this too, using just ">= 3 && < 4" etc.
And yet version numbers of base have 4 components -- I think the situation is unclear, and we need a clear statement if these constraints are to be meaningful. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/435#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects