Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Aug 2002 14:02:07 -0700
From:      "Brian Li" <brian_li@hotmail.com>
To:        <freebsd-newbies@freebsd.org>
Cc:        <freebsd-newbies@freebsd.org>
Subject:   Re: Using CVSup
Message-ID:  <OE60NcMtLoOnY3aFgrj00007d69@hotmail.com>
References:  <019d01c23fd7$2d44d740$272fa8ce@jim> <01c101c23fd8$78b4b5f0$272fa8ce@jim> <3D54162F.1000502@xmission.com> <3D541E31.C8A0EB52@pantherdragon.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I am new to FreeBSD. I am still confuse with the naming convention. Stable
should be more stable than regular release. Howvever, according to the
handbook, it seems like it is not the case. Then why call it stable?

----- Original Message -----
From: "Darren Pilgrim" <dmp@pantherdragon.org>
To: "Jason Porter" <leporter@xmission.com>
Cc: <freebsd-newbies@freebsd.org>
Sent: Friday, August 09, 2002 12:55 PM
Subject: Re: Using CVSup


> Jason Porter wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Stable has more fixes in it than Release.  Release means that it's
> > release quality.  They can safely box it and ship it out.  Stable has
> > the same base as the Release version but contains fixes and is okay to
> > use on a production server (in theory).
>
> Not true.  If you read the Handbook section on -stable, it says in
> implied huge, red, flashing letters that there is absolutely no
> guarantee that stable will even compile.
>
> Yes, a lot of people use -stable on production servers.  I'm one of
> them.  But the tricks to do this safely, the list of gotchas, and the
> constant list monitoring needed to no screw the machine up is not
> something I would consider a habit a beginner should be getting into
> just yet.
>
> A happy medium between the RELEASE tags and -STABLE are the RELENG_4_x
> tags.  It's the release (RELENG_4_6 == 4.6) source with all the
> relevant patches from the SA's applied.  I would consider this a safe
> way to get your feet wet with cvsup and the make world process, as
> there's very little to trip over with the mergemaster process (perhaps
> the most dangerous part of the whole deal).
>
> > |>Here's my supfile:
> > |>
> > |>*default host=cvsup8.freebsd.org
> > |>*default base=/usr/local/etc/cvsup
> > |>*default prefix=/usr
> > |>*default release=cvs
> > |>*default deltee use-rel-suffix
>              ^^^^^^ should be "delete"
> > |>*default tag=RELEN_4_6_1_RELEASE
>                  ^^^^^ - should be "RELENG"
> > |>src-all
> > |>*default tag=.
> > |>ports-all
> > |>doc-all
>
> Giving more than one value for a default isn't good practice, IMO.
> Here's how I would have specified it:
>
> *default tag=.
> src-all tag=RELENG_4_6_1_RELEASE
> doc-all
> ports-all
>
> I'd recommend seperating ports-all into its own supfile and update it
> only after the new world is installed and working.  You really want to
> have your system as coherent and stable as possible while building and
> installing the world.  When you pull down the ports tree, you can get
> all kinds of problems that turn into a gang of hungry sharks should
> you run into problems with the world upgrade and need to majorly
> rebuild your system.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-newbies" in the body of the message
>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-newbies" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?OE60NcMtLoOnY3aFgrj00007d69>