Date: Fri, 12 Feb 1999 11:39:25 -0800 (PST) From: asami@FreeBSD.ORG (Satoshi Asami) To: kkennawa@physics.adelaide.edu.au Cc: bmah@ca.sandia.gov, freebsd-ports@FreeBSD.ORG Subject: Re: package build errors Message-ID: <199902121939.LAA94744@silvia.hip.berkeley.edu> In-Reply-To: <Pine.OSF.4.05.9902122338220.11786-100000@bragg> (message from Kris Kennaway on Fri, 12 Feb 1999 23:42:35 %2B1030 (CST))
next in thread | previous in thread | raw e-mail | index | archive | help
* I was thinking about this the other day - people have been finding * recently that some of the BROKEN ports are actually in perfect working order, * since the conditions which caused them to be marked as such have gone away * (transient net problem, change in the FreeBSD source tree that fixes the * problem, or just committer error). * * Including ports which are marked BROKEN in your automatic package building * would discover these false negatives (at the expense of building probably lots * of packages which are legitimately broken). You know, I was thinking the exact same thing recently. :) I just made a change that will let the next full build descend into the BROKEN ports too. Unfortunately, that will be the final build before 3.1R. I hope there isn't any nasty side effects on this. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902121939.LAA94744>