Date: Tue, 28 Oct 2003 18:37:22 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Jason Williams <jwilliams@courtesymortgage.com> Cc: freebsd-questions@freebsd.org Subject: Re: Clarification on CVS Tags Message-ID: <20031028183722.GA13189@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <5.2.1.1.0.20031028085609.00afa820@pop.courtesymortgage.com> References: <5.2.1.1.0.20031028085609.00afa820@pop.courtesymortgage.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nFreZHaLTZJo0R7j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Oct 28, 2003 at 09:43:20AM -0800, Jason Williams wrote:
> Good morning everyone.
>=20
> I was hoping to get some verification regarding CVS Tags. I'm pretty sure=
I=20
> understand, but just wanted to have my thoughts validated for me.
>=20
> In reading the CVS Tag page in the handbook, I understand the basics of=
=20
> what is going on.
>=20
> If I specify this in my cvsup file:
> RELENG_4_8
>=20
> I will follow the Release Branch of 4.8, plus security patches.
> This would be a good choice for production servers.
Correct.
=20
> RELENG_4
> For this, you are following the entire 4.x stable branch. In theory, if I=
=20
> install 4.5 and set this up in my cvsup file and run it, I will have the=
=20
> source tree going all the way to 4.9rc# correct? From here, you could bui=
ld=20
> world?
Correct. At the moment, RELENG_4 will get you 4.9-RC4, which will
shortly become 4.9-RELEASE for a few minutes while the RELENG_4_9
branch is created, and then 4.9-STABLE.
If you're willing to wait for a few days RELENG_4_9 would also be a
good choice for a production server.
> Finally:
>=20
> RELENG_4_8_0_RELEASE
>=20
> This would follow just the source, ports and docs tree up to 4.8, the=20
> "frozen" section, correct?
> Why would someone want to use this particular setup? What are the benefit=
s?=20
> Drawbacks?
> Would it work in a sense that if I installed 4.4 on a server, set this up=
=20
> in my cvsup file to RELENG_4_8_0_RELEASE, ran the update to update source=
s,=20
> ports and docs, then make world: That then would make my box 4.8 ?
Not so correct. RELENG_4_8_0_RELEASE marks the state of the system
sources at the point that the RELENG_4_8 branch was created, and what
went onto the release CDs. Yes, you can use this tag to download
sources and building world from there will get you 4.8-RELEASE.
However, it's not generally useful to put this tag into a cvsup
sup-file -- principally because it marks a point in time, and once
you've downloaded it, there won't be any updates. So: no security
patches etc. If you're tempted to use this tag, then you probably
really want to use RELENG_4_8 or RELENG_4_9 instead.
Note that the RELENG_4_x and RELENG_5_x tags apply only to the system
sources. The one important tag you've not mentionned is '.', also
known as the HEAD in cvs terms. When applied to the system sources,
this gets you 5-CURRENT, but unless you're a high powered system
hacker type, you don't want that.
Ports and docs however, are a different matter. For those collections
'.' is the only game in town. The RELENG_x_y tags simply don't exist,
and if you accidentally try and cvsup ports using one of them, you'll
end up deleting your whole ports tree. [The RELENG_x_y_0_RELEASE tags
do exist, but exactly like the system sources they just serve to mark
what goes onto the CD Roms.]
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--nFreZHaLTZJo0R7j
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/nrdidtESqEQa7a0RAqmFAJ4kTrj0+GrH81+zSuFunD9CU1MvmQCgkLL3
WuMVpd+9aZXzy/AsF8q/mtU=
=RgFF
-----END PGP SIGNATURE-----
--nFreZHaLTZJo0R7j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031028183722.GA13189>