On Thu, Jul 23, 2009 at 6:42 PM, Trent W. Buck <[email protected]>wrote:
> Eric Kow <[email protected]> writes: > > So we could *still* try to keep the zlib code around, only this time > > agree to get rid of it, when it is a demonstrably an impediment to > > progress. > > Consider the case where a user reports a strange bug that none of us can > reproduce. After weeks of discussion, it finally is discovered that > zlib 0.5.0 was installed on that user's system, so cabal silently picked > -f-zlib. That user was using the internal zlib instead of libHSzlib. > > This actually happened to me -- if I hadn't bothered to configure > --verbose and check the flags, I would be running the internal zlib > right now and not even know it. Good point. I think we may want to check if cabal has a 'deprecation' warning it can give for certain options or combinations of options. If so, we could use that. I guess we could even implement it as a hook, but if we go to that much trouble we might as well just get rid of this zlib. Jason
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
