Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Apr 2001 12:07:01 +0100
From:      Nik Clayton <nik@freebsd.org>
To:        Dan Langille <dan@langille.org>
Cc:        Christopher Schulte <christopher@schulte.org>, Matthew Emmerton <matt@gsicomp.on.ca>, Rasputin <rara.rasputin@virgin.net>, stable@FreeBSD.ORG
Subject:   Re: Releases
Message-ID:  <20010410120701.A749@canyon.nothing-going-on.org>
In-Reply-To: <Pine.BSF.4.32.0104100522430.38514-100000@xeon.int.nz.freebsd.org>; from dan@langille.org on Tue, Apr 10, 2001 at 05:29:43AM %2B1200
References:  <5.0.2.1.0.20010409111054.00b18008@pop.schulte.org> <Pine.BSF.4.32.0104100522430.38514-100000@xeon.int.nz.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--sm4nu43k4a2Rpi4c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 10, 2001 at 05:29:43AM +1200, Dan Langille wrote:
> On Mon, 9 Apr 2001, Christopher Schulte wrote:
> > At 03:45 AM 4/10/2001 +1200, Dan Langille wrote:
> > >Give meaningful and widely used names to things which people are famil=
iar
> > >with.
> >
> > -CURRENT fits all those requirements.
>=20
> In this case, the familiarity is reduced to those familiar with the
> project.  Witness the frequency with which the confusion
> arises.

It's question five in the FAQ. =20

    http://www.freebsd.org/FAQ/preface.html#CURRENT

The first para says "only of interest to developers working on the
system and die-hard hobbyists".

The second para says

    If you are not familiar with the operating system or are not capable of
    identifying the difference between a real problem and a temporary=20
    problem, you should not use FreeBSD-CURRENT. This branch sometimes
    evolves quite quickly and can be un-buildable for a number of days at a
    time. People that use FreeBSD-CURRENT are expected to be able to analyz=
e=20
    any problems and only report them if they are deemed to be mistakes=20
    rather than ``glitches''. Questions such as ``make world produces some=
=20
    error about groups'' on the -CURRENT mailing list are sometimes treated=
=20
    with contempt.

I don't see any way in which someone could start running -current
without seeing that warning, or the equivalent warnings in the Handbook.

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.

N
--=20
FreeBSD: The Power to Serve             http://www.freebsd.org/
FreeBSD Documentation Project           http://www.freebsd.org/docproj/

          --- 15B8 3FFC DDB4 34B0 AA5F  94B7 93A8 0764 2C37 E375 ---

--sm4nu43k4a2Rpi4c
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjrS6VQACgkQk6gHZCw343WJsQCfQDdcdJiPSFStiCkokrtRV5Zq
JdoAn3ltsJ2jmL/E0bx30Ny1BHHTpU7X
=aM4c
-----END PGP SIGNATURE-----

--sm4nu43k4a2Rpi4c--

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?20010410120701.A749>