I am almost embarrassed to say this. But on ports, you want
-current. So if you have one long cvs file, half way through you have to
change the default tag so you sup -current for ports. Thus is says in
/usr/share/examples/cvsup/4.x-stable-supfile:
###############################################################################
#
# DANGER! WARNING! LOOK OUT! VORSICHT!
#
# If you add any of the ports collections to this file, be sure to
# specify them like this:
#
# ports-all tag=.
#
# If you leave out the "tag=." portion, CVSup will delete all of
# the files in your ports tree. That is because the ports collections
# do not use the same tags as the main part of the FreeBSD source tree.
#
###############################################################################
In short, If you already suped current for ports, you should just
leave them that way. That at least is right.
-Marius M. Rex
On Mon, 4 Dec 2000, Jason Watkins wrote:
> what about /ports
>
> is it not a big deal if I loose any state that's saved in there for the
> ports I have installed, and I should just blast all of that as well, or can
> I trust cvs to overright -current with -stable... or does that forking not
> apply to the ports collection at all.
>
> jason
>
>
---------------------
Marius
Community Connect Inc.
Desk = 212.644.3718 ext: 222 (infrequently manned)
cell = 347.386.4345
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
