Date: Mon, 19 May 2003 01:56:38 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Joerg Wunsch <joerg@FreeBSD.org> Cc: ports-committers@FreeBSD.org Subject: BROKEN tags (Re: cvs commit: ports/devel/avr-libc Makefile) Message-ID: <20030519085637.GA71335@rot13.obsecurity.org> In-Reply-To: <200305190828.h4J8S8l0069634@repoman.freebsd.org> References: <200305190828.h4J8S8l0069634@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 19, 2003 at 01:28:08AM -0700, Joerg Wunsch wrote: > joerg 2003/05/19 01:28:08 PDT >=20 > FreeBSD ports repository >=20 > Modified files: > devel/avr-libc Makefile=20 > Log: > 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. Perhaps you could update the error message to be more descriptive of the problem, but it should remain BROKEN until it can again be compiled successfully. The point of the BROKEN tag is to provide a message to prospective users of the port that there are known problems with the software. If it's not there, then they will encounter confusing compilation failures when they go to build the port, and among other things this looks bad for FreeBSD. Thanks, Kris --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+yJxFWry0BWjoQKURAvLeAKCTA0x7ShBoFkWa/nKe+YfV7cS7FQCfVtIF ogUkfDOFu4pgV6k/RkAU/OM= =MfO/ -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519085637.GA71335>