On Fri, Mar 02, 2012 at 02:46:53PM +0100, Alessandro Pezzoni wrote: > > `ghc-paths` used to be in [extra]/[community] at some point, I wonder > > why it was removed. > > I tried adding it to habs but I couldn't do that, because it is > already there as a base package. I can't remove it either without > removing all its dependants first. > Should I leave this alone until we figure out why it was removed?
I've just made an attempt at adding ghc-paths to [haskell], but I failed because [extra]/[community] is broken: - one of the packages that depend on ghc-paths also depends on deepseq, and - deepseq is gone from [extra]/[community], so I added it too to [haskell], but - one of the packages that depend on deepseq also depends on text, and - text in [extra]/[community] depend on deepseq This effectively prevents me from fixing [haskell] until [extra]/[community] is fixed! This episode has made me consider whether the tight dependency between [haskell] and [extra]/[community] should be broken in the future. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: [email protected] jabber: [email protected] twitter: magthe http://therning.org/magnus Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. -- Alan Kay
pgp2rDKYhQV3a.pgp
Description: PGP signature
_______________________________________________ arch-haskell mailing list [email protected] http://www.haskell.org/mailman/listinfo/arch-haskell
