BROKEN tags (Re: cvs commit: ports/devel/avr-libc Makefile)
kris at obsecurity.org
Mon May 19 02:37:09 PDT 2003
On Mon, May 19, 2003 at 11:16:49AM +0200, Joerg Wunsch wrote:
> As Kris Kennaway wrote:
> > > Remove BROKEN. It's not that port that is broken, but FreeBSD 5.x in
> > > that it has broken /again/ all cross-compilation attempts. Whoever
> > > broke it ought to fix that.
> > BROKEN indicates that the port does not compile. While I agree with
> > you that the fault lies with bsd.cpu.mk, this fact remains true.
> Still, by now, the policy has been that whoever broke the system is
> repsonsible for fixing it. If someone breaks buildworld, we don't
> mark the entire system `broken', but require him to fix the breakage.
I'm not debating the nature of the problem or who should fix it. As
you know, I cc'ed the committer on the message where I identified the
commit that introduced the problem.
Instead of looking at this issue as "Committer X broke my port, so why
should I have to put up with a BROKEN message in my port for something
that wasn't my fault?" try to see it in terms of the end user -- you
know, the guy out there for whom we're all supposed to be providing an
OS. He or she just wants to install the software and doesn't care
which unknown person caused the problem, only that it exists and is a
known bug that prevents the port from building, so they shouldn't
waste their time trying.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-ports/attachments/20030519/4c9f48c9/attachment.bin
More information about the cvs-ports