I believe there was a discussion a while back, and if you used this:
.if ${ARCH} == sparc64
BROKEN= does not compile on sparc64: assertion failed
.endif
it is POSSIBLE that cluster runs that test broken ports could fix them
(accidentally), but, wasn't the opinion that you might as
On 4/10/12 5:16 AM, Erwin Lansing wrote:
maintainer that something is wrong.
There are quite a few large grey areas between those, but that's the
general outline.
so, if the maintainer knows something, and knows it won't ever get
fixed, then 'NOT_FOR_ARCHS' is best,
if its an unknown/ maybe
On 10 Apr 2012 10:33, Michael Scheidell scheid...@freebsd.org wrote:
On 4/10/12 5:16 AM, Erwin Lansing wrote:
maintainer that something is wrong.
There are quite a few large grey areas between those, but that's the
general outline.
so, if the maintainer knows something, and knows it
On Tue, Apr 10, 2012 at 11:16:19AM +0200, Erwin Lansing wrote:
BROKEN is for less permanent or unknown breakage, like errors on pointyhat
where the one analyzing the logs doesn't have detailed knownledge of each
port and its breakage, and is used as a warning to users, so they don't try
to
