Bryan O'Sullivan wrote: > This feels like a big piece of work to be pushing in right before a release.
+1 > It worries me because now there's an invisible piece of metadata floating > around that neither OS packagers nor library maintainers can see. In a way, > this feels strictly worse than having a package just plain break, because > it's not hard to imagine a cycle of "package breaks; magic invisible > dependency update silently fixes it; new version is released; package > re-breaks because maintainer never found out about previous breakage". Yep, this idea seems potentially problematic. > I could be convinced that in fact everything is going to be awesome and it > will all somehow work, but in the short term I'd prefer to delay sprinkling > invisible dependency pixie dust on packages, and let this wait until the > next release, 3 months down the line. +1 Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/ _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
