Date: Sun, 27 Nov 2005 10:18:34 +0530 From: Joseph Koshy <joseph.koshy@gmail.com> To: Josh Paetzel <josh@tcbug.org> Cc: freebsd-doc@freebsd.org Subject: Re: cvsup-advanced article Message-ID: <84dead720511262048o7ce9c91dicae58bf44c1dd447@mail.gmail.com> In-Reply-To: <200511261346.26050.josh@tcbug.org> References: <17489c7a0511260006o156e9d81o6853e9c0a1e3b183@mail.gmail.com> <84dead720511260449u165a7bf2x1bd41e06e3a8efaf@mail.gmail.com> <200511261346.26050.josh@tcbug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
jp> I thought the tag for ports was . It is, if you wish to track ports development. My understanding is that the ports tree on the ISO image corresponds to CVS tag RELEASE_X_Y_Z, so the first time around you would specify that when running CVSup. This step will only create a "checkouts.cvs:RELEASE_X_Y_Z" file since nothing else needs to be done on the local file system. Now if you edit your cvsupfile to require "tag=3D.", and rename "checkouts.cvs:TAG_NAME" to "checkouts.cvs:.", when CVSup runs it will look for "checkouts.cvs:." and will find it. It will then update the local filesystem and its checkouts.cvs database in the usual way. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84dead720511262048o7ce9c91dicae58bf44c1dd447>