Hello In many invidual projects one is faced with challenges from the changing standard library. Currently it seems that each project uses a separate solution - maybe a common approach would be possible. I would be most interested in packaging a library which would implement GHC 6.4 base package for older releases (mainly GHC 6.2.x). GHC seems to have its own solution in fptools/ghc/lib/compat/ but having a cabal package and supporting e.g. Data.Map/Set could make things easier. Does this sound like a good idea or is there a much better solution? - Einar Karttunen
Einar Karttunen
GHC seems to have its own solution in fptools/ghc/lib/compat/ but having a cabal package and supporting e.g. Data.Map/Set could make things easier. Does this sound like a good idea or is there a much better solution?
I think it's a good idea. It would be nice to have a single Cabal package for all the differences between 6.2 and 6.4, including HUnit, Data.Queue, and others. It would certainly be useful to me, since I still use 6.2 for some stuff, but I don't know how many ppl are like me. Of course, it would be better to have multiple Cabal packages, but Cabal doesn't implement inter-dependent packages in one .cabal file yet. I hope to soon! peace, isaac
participants (2)
-
Einar Karttunen -
Isaac Jones