Date: Wed, 26 Dec 2001 16:42:33 +0100 From: Gerhard Sittig <Gerhard.Sittig@gmx.net> To: freebsd-stable@freebsd.org Subject: Re: RELENG_4_5 Message-ID: <20011226164233.R1494@shell.gsinet.sittig.org> In-Reply-To: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de>; from hausen@punkt.de on Wed, Dec 26, 2001 at 03:01:43PM %2B0100 References: <200112261401.fBQE1hb47452@hugo10.ka.punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 26, 2001 at 15:01 +0100, Patrick M. Hausen wrote:
>
> Just a minor question: at which point in the 4.5 release cycle
> will a RELENG_4_5 tag appear?
Apparently when release 4.5 *did* appear. That's how things were
designed and done up to now. :)
> I'd be more than happy to test
> -PRERELEASE and/or -BETA on a couple of machines, but I'd rather
> change my cvsupfiles from RELENG_4_4 to RELENG_4_5 than RELENG_4.
> Saves me from changing them back after -RELEASE.
How about cvsupping the CVS repo instead? This
- will not clobber your source tree with a snapshot
- allows you to "cvs co -rANY_TAG_YOU_LIKE"
- allows you to hold several versions locally e.g. on several
machines (read: keep your production machines at RELENG_4_4
and yet check RELENG_4 for suitability on test machines)
- allows you to have local fixes and enhancements (not yet MFCed
stuff, features you invent yourself :), features you want but
the project doesn't accept, bugfixes you haven't verified to
fix the bug yet and thus haven't fed back to the project, and
many other things you can imagine)
- allows you to follow the development process without having
to actually live on the bleeding edge -- you have the repo to
watch (log, diff, up -p, etc) and you can decide which date's
version you want to compile and use; this might be required for
-CURRENT but comes in handy for -STABLE sometimes, too, since
there's some jitter time after time
The alternative could be to copy your source tree (to keep the
RELENG_4_4 version intact) and redirect your cvsup config file
to the new location while telling it to sync against the RELENG_4
tag. Or maybe you can even override the needed attributes on
the command line.
But it looks like keeping a local repo is the easiest and most
efficient way. Start with the repo from the second CD and update
it by means of cvsup (release=cvs). Extracting a source tree is
as easy as doing "cvs co -rRELENG_4 src" once and "cvs up" as
often as you please. See "man cvs" for details. Or talk to me
privately for more help.
> Wouldn't it make sense if -BETAs and -RCs were already tagged
> RELENG_4_X?
NO! The whole point in the RELENG_4_X tags is to stamp them on
"release code plus essential security fixes". Even show stopper
bugs aren't considered appropriate when they are not security
related. You wouldn't consider -BETAs and -RCs equivalent to
release code, would you? Most users don't want to use -BETAs
in production either (no matter how you judge free software
betas against some comercial releases :).
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
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?20011226164233.R1494>