BROKEN tags (Re: cvs commit: ports/devel/avr-libc Makefile)
kris at obsecurity.org
Mon May 19 03:53:26 PDT 2003
On Mon, May 19, 2003 at 11:43:41AM +0200, Joerg Wunsch wrote:
> As Kris Kennaway wrote:
> > 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.
> The end user could always remove (or empty) /usr/share/mk/bsd.cpu.mk
> himself, and get the port to compile. With the BROKEN line, he still
> wouldn't be able to compile an otherwise fully functional port.
Don't be silly..if the user is willing to perform major surgery on a
system makefile, then they can just as easily make the trivial change
to comment out or remove the BROKEN tag from the port makefile.
-------------- 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/cfa87aa3/attachment-0001.bin
More information about the cvs-ports