Date: Mon, 19 May 2003 11:43:41 +0200 From: Joerg Wunsch <j@uriah.heep.sax.de> To: Kris Kennaway <kris@obsecurity.org> Cc: ports-committers@freebsd.org Subject: Re: BROKEN tags (Re: cvs commit: ports/devel/avr-libc Makefile) Message-ID: <20030519114341.B2937@uriah.heep.sax.de> In-Reply-To: <20030519093706.GA90624@rot13.obsecurity.org>; from kris@obsecurity.org on Mon, May 19, 2003 at 02:37:06AM -0700 References: <200305190828.h4J8S8l0069634@repoman.freebsd.org> <20030519085637.GA71335@rot13.obsecurity.org> <20030519111649.A2937@uriah.heep.sax.de> <20030519093706.GA90624@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519114341.B2937>