Date: Tue, 8 Jan 2008 09:57:27 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Frank Shute <frank@esperance-linux.co.uk> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: port collection RELEASE6.2 lost after reinstall with CVSUP Message-ID: <20080108085727.GA28225@owl.midgard.homeip.net> In-Reply-To: <20080107035841.GA44545@melon.esperance-linux.co.uk> References: <000601c85065$94c24de0$0a01a8c0@680nr0j> <20080106200517.GA42384@melon.esperance-linux.co.uk> <20080106202415.GA97410@owl.midgard.homeip.net> <20080107035841.GA44545@melon.esperance-linux.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 07, 2008 at 03:58:41AM +0000, Frank Shute wrote: > On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote: > > > > On Sun, Jan 06, 2008 at 08:05:17PM +0000, Frank Shute wrote: > > > On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote: > > > > > > > > Hi > > > > > > > > Upon reading chapters of the Handbook about the Ports collection > > > > and CVSup, I wanted to CVSup the ports collection for the > > > > RELEASE 6.2. Stupidly using the wrong tag (tag=.), I > > > > erroneously but successfully installed the CURRENT version. I > > > > could have used SYSINSTALL for the RELEASE 6.2 ports, but for > > > > the sake of learning and training myself I did not. > > > > > > You used the right tag. There is only a current tag as you only have a > > > current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The > > > ports might work with older releases too). > > > > Wrong. The ports tree is not branched, but it is tagged and it does have > > tags corresponding to each FreeBSD release. > > So if it's not branched but tagged, what's the difference between the > ports tree I get if I use RELENG_4_8 compared to RELENG_7_0 as tags > in my ports supfile? None whatsoever. Neither tag is a valid tag for the ports tree, so you will end up with an empty ports tree in either case. If you were instead to use the valid tags RELEASE_4_8_0 or RELEASE_7_0_0 you would get the ports tree that shipped with 4.8-RELEASE or the ports tree that will (barring last minute changes) ship with 7.0-RELEASE respectively. > > > > > > > > Problem: > > > > > > > > - I ran CVSup again with the correct tag but though everything > > > > in the process looked normal, the map usr/ports remains empty > > > > and nor with whereis nor with pkg_xxx any information about > > > > ports can be found. > > > > > > You ran cvsup again with the wrong tag. > > > > > > > > > > > Questions: > > > > > > > > - What did I do wrong in the process?. > > > > > > Used the wrong tag second time around. > > > > > > > > > > > - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea > > > > anyway (technically) ? > > > > > > No. Although there is no 6.2 ports collection, just CURRENT. > > > > Of course there is a 6.2 ports collection. What else would you call the > > ports tree shipped with FreeBSD 6.2? > > A snapshot of the ports tree when the release was made. > > > > > > > > > > > > > > > > > > > > > > > > Proces: > > > > > > > > - I use the recently installed cvsup-without-gui, installed from ports > > > > > > Use csup(1) it's identical to cvsup but no dependencies as it's in > > > base & written in C. > > > > Not quite identical. There are a couple of features that cvsup(1) has, but > > which csup(1) does not yet have. > > To just check out a copy of the ports tree either should work fine though. > > Features that a newbie wouldn't use. It's also difficult to build > cvsup when you don't necessarily have a ports tree. But you do not need a ports tree to install cvsup as a package. In either case csup(1) is not identical to cvsup(1) in functionality even if it can often be used as a drop-in replacement. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080108085727.GA28225>