If packages are patched without any change in version number,
bad things can happen if one tries to cabal install additional packages
onto such a patched ghc.
At the moment, that seems to be the case for array and containers,
which were adjusted following the syb split, without changes in version
number (containers also seems to have gained some exports, foldrWithKey
and the like, again without version bump). Could this please be fixed?
What happens currently is that cabal notices that it has different
array/containers packages with the same version number, and
decides to reinstall the ones from hackage over the ones in the
head build (which can then cause packages depending on the
newer versions to fail linking).
While cabal's behaviour is somewhat suspect in this case, it cannot
be blamed for the wrong version numbers. See this thread for details
http://www.haskell.org/pipermail/cvs-ghc/2008-December/046615.html
Perhaps darcs could help to remind submitters of version bumps
(without automation, this kind of thing is hard to remember):
http://www.haskell.org/pipermail/cvs-ghc/2008-December/046643.html
Claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
