Date: Sun, 06 May 2007 21:05:35 +0200 From: Martin Hudec <corwin@aeternal.net> To: 'FreeBSD Questions' <freebsd-questions@freebsd.org> Subject: Re: CVS release tag for current patched release Message-ID: <463E26FF.8030507@aeternal.net> In-Reply-To: <2AD6FC99-694F-4633-8945-771CFA7B35EA@goldmark.org> References: <2AD6FC99-694F-4633-8945-771CFA7B35EA@goldmark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeffrey Goldberg wrote: > The short version of my question is whether the cvs tag RELENG_6_2 > refers to the latest on the 6.2 STABLE branch or the 6.2 RELEASE Branch. RELENG_6 - actual -STABLE RELENG_6_2 - actual -RELEASE-pX -RELEASE are taken off -STABLE at predefined times, and as such we can say, that -RELEASE is snapshot from -STABLE at the date of new release. Development is being done in -STABLE. So if you want to have current release with it's patchlevels as they are, use RELENG_6_2. > I wish to make some minor local modifications to my system running 6.2 > RELEASE p4. So far, I've been maintaining my system using csup with a > sup file based on > > /usr/share/examples/cvsup/standard-supfile > > But my local changes get overwritten with each new update using csup. I > was advised earlier on this list to use cvs instead (which I thought > csup did, but now I see that csup (and cvsup) will use "checkout" mode > instead of "CVS mode" unless I'm on the bleeding edge. Copy this file somewhere else, like /usr/local/etc and modify it as you need. Whole cvsup command would look like: # cvsup -L 2 /usr/local/etc/stable-supfile kind regards, Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?463E26FF.8030507>