
On Mon, Aug 27, 2012 at 09:03:18PM +0100, Brent Yorgey wrote:
On Mon, Aug 27, 2012 at 10:52:59AM -0700, Bryan O'Sullivan wrote:
On Mon, Aug 27, 2012 at 9:57 AM, Erik Hesselink
wrote: I'm seeing this again, on abstract-deque-0.1.6. Ross, can you fix it again?
Hang on a second.
The reason you're seeing build breakage is that the .cabal files of the broken packages were edited in-place without communicating with any of the package authors.
I understand that the collective intentions around this were good, but by "fixing" things without telling anyone, package maintainers have no way to know that anything has happened. Now we are seeing the problem begin to recur as people issue new releases that don't incorporate those changes.
For the record, abstract-deque was neither one of the packages fixed previously, nor does its .cabal file even contain a test section at all, much less one with a conditional.
It did a couple of hours ago.
But I agree with Bryan in principle that we need a more principled approach.
Yes, and Cabal is the place to test for this.