Re: dating a ports tree

2004-03-19 Thread Scott K. Benolkin
Thank you for your answer.  I learned something, but I still appear to be
missing something obvious.  My supfile is appended below.  Using the line

*default tag=RELENG_5_2_1_RELEASE list=cvs:RELENG_5_2

works as I anticipate for src-* collections, creating checkout files with
the appropriate name.  However, even with the line

*default tag=RELENG_5_2_1_RELEASE list=cvs:.

above the ports-* collections, this supfile results in cvsup deleting all
the files in my ports tree.

Scott

Quoth Kris Kennaway:
> 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
> 
> 

*default host=cvsup12.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs
*default delete use-rel-suffix
#*default compress
#*default tag=RELENG_5_2
*default tag=RELENG_5_2_1_RELEASE list=cvs:RELENG_5_2
src-base
src-bin
src-contrib
src-crypto
#src-eBones
src-etc
src-games
src-gnu
src-include
#src-kerberos5
#src-kerberosIV
src-lib
src-libexec
src-release
src-sbin
src-secure
src-share
src-sys
src-sys-crypto
src-tools
src-usrbin
src-usrsbin
#*default tag=.
*default tag=RELENG_5_2_1_RELEASE list=cvs:.
#ports-all
ports-base
ports-accessibility
#ports-arabic
ports-archivers
ports-astro
ports-audio
ports-benchmarks
ports-biology
ports-cad
#ports-chinese
ports-comms
ports-converters
ports-databases
ports-deskutils
ports-devel
ports-dns
ports-editors
ports-emulators
ports-finance
#ports-french
ports-ftp
ports-games
#ports-german
ports-graphics
#ports-hebrew
#ports-hungarian
ports-irc
#ports-japanese
ports-java
#ports-korean
ports-lang
ports-mail
ports-math
ports-mbone
ports-misc
ports-multimedia
ports-net
ports-news
ports-palm
ports-picobsd
#ports-polish
#ports-portuguese
ports-print
#ports-russian
ports-science
ports-security
ports-shells
ports-sysutils
ports-textproc
#ports-ukrainian
#ports-vietnamese
ports-www
ports-x11
ports-x11-clocks
ports-x11-fm
ports-x11-fonts
ports-x11-servers
ports-x11-toolkits
ports-x11-wm

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: dating a ports tree

2004-03-16 Thread Kris Kennaway
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



pgp0.pgp
Description: PGP signature


dating a ports tree

2004-03-16 Thread Scott K. Benolkin
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.

Please CC to my address.  Thank you for your time and knowledge/cleverness.

Scott

-- 
"Frederick, is God dead?" --Sojourner Truth

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"