Date: Tue, 16 Mar 2004 14:23:26 -0800 From: Kris Kennaway <kris@obsecurity.org> To: "Scott K. Benolkin" <beno0028@umn.edu> Cc: freebsd-questions@freebsd.org Subject: Re: dating a ports tree Message-ID: <20040316222326.GA50465@xor.obsecurity.org> In-Reply-To: <200403161925.i2GJPXxf006323@fantasy.software.umn.edu> References: <200403161925.i2GJPXxf006323@fantasy.software.umn.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 16, 2004 at 01:25:33PM -0600, Scott K. Benolkin wrote: > For CVSuping a ports tree (e.g., the ports distribution from a release CD) > for the first time (i.e., no preexisting checkouts file), section 4.3 of > Salvo Bartolotta's "CVSup Advanced Points" article > (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/cvsup-advanced/article > .html) > recommends, "you should specify a date as close as possible to that of > `shipping' of your ports tree." It's easy enough to do this roughly, but > I'm curious if anyone knows an "official" (or at least surefire) way to > easily and precisely determine the "shipping" date of a ports tree > (realizing that the "date" keyword will specify a time down to the second). > I'm not trying to say this is essential, but if there's a best practice, > I'd like to know. cvsup to the tag of the release you are installing. See the handbook for information about cvsup tags. Kris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAV35eWry0BWjoQKURAta4AKCcpLEXyfi8vxaSnV8bMd2vvOWQ6QCeNPH7 XTlxXaLa3b6qwfDASQLMLX4= =2xWB -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040316222326.GA50465>