Date: Tue, 11 Jun 2002 16:20:18 +0100 From: Pete French <pfrench@firstcallgroup.co.uk> To: stijn@win.tue.nl Cc: stable@freebsd.org Subject: Re: code freeze Message-ID: <E17HnRS-000MCX-00@mailhost.firstcallgroup.co.uk> In-Reply-To: <20020611165559.A34669@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> You can always use cvs to checkout the ports tree with tag RELEASE_4_6_0, > although I also thought that cvsupping with that same tag would work. click! I am truly an idiot! - was using RELENG_4_6_0 - all fine now. > But just one quick question: why do you really need the *exact* ports tree > for 4.6? I'd think the current ports tree is better - ports get upgraded all > the time, there's nothing special about the ports tree at the tagging moment. Well, as you point out, I dont need the exact 4.6 set - but what I am after is a reference point so that I can make sure all subsequent machines I install get the same versions of the ports as we are going to be (gradually) switching 7 or 8 machines over from NT4 to FreeBSD in the comming month or so. I can keep all the operating systems in sync by cross-mounting /usr/src, but I have a local ports tree on each machine and I want an easy way to be able to do a 'cvsup' and take them all to exactly the same version (including a couple of existing machines runnng 4.4-RC and 4.5-STABLE which need upgrading). The 4.6 release point looks like a good candidate for this, and also means that any new machines installed off the 4.6 ISO willl get the same versions of the software. I'm sure theres probably a way to have a single /usr/ports NFS mounted and to be able to do a 'make install' onto several machines, but if so I havent found it... :-) -pcf. 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?E17HnRS-000MCX-00>