Date: Tue, 10 Apr 2001 07:52:06 -0500 From: Mike Meyer <mwm@mired.org> To: Nik Clayton <nik@freebsd.org> Cc: stable@freebsd.org Subject: Re: Releases Message-ID: <15059.502.493117.364068@guru.mired.org> In-Reply-To: <20010410120701.A749@canyon.nothing-going-on.org> References: <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <Pine.BSF.4.32.0104100522430.38514-100000@xeon.int.nz.freebsd.org> <20010410120701.A749@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nik Clayton <nik@freebsd.org> types: > I don't see any way in which someone could start running -current > without seeing that warning, or the equivalent warnings in the Handbook. More than once people have shown up on -questions running -current because they just grabbed the "standard" supfile. Which gets them -current :-(. Which was why I suggested that it standard-supfile get the branch being run. > Short of making -current refuse to build without a magic cookie in > /etc/make.conf, and a webpage that contains that cookie along with this > dire warning, I don't see how we can make it more obvious to people that > they shouldn't be running -current if they don't know what they're doing. It would help if they had to read those docs before having a supfile that could be used to grab -current without editing the supfile. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15059.502.493117.364068>