-----Original Message-----
From: John Bleichert <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Thu, 17 Oct 2002 09:10:21 -0400 (EDT)
Subject: CVSup world/ports

<From Mike Hogsett's excellent CVSup post>: 
>> cp /usr/share/examples/cvsup/standard-supfile /etc/standard-supfile
>
>edit /etc/standard-supfile
>
>change :
>
>*default host=CHANGE_THIS.FreeBSD.org
>
>Set "CHANGE_THIS.FreeBSD.org" to a "close" cvsup server.  By close I mean
>one that has either a good ping or the fewest hops in traceroute.
>
>Here in Silicon Valley I used to get great speeds from 
>cvsup14.FreeBSD.org until I started running my own cvsup mirror, now I 
>use my mirror.
>
>change :
>
>*default release=cvs tag=RELENG_4_7
>
>**NOTE** "RELENG_4_7" will likely be different in your copy of
>standard-supfile.  Change it to be "RELENG_4_7".  This is the 4.7 with
>patches branch (a good one to track).
>
>run :
>
>> cvsup -g /etc/standard-supfile
>
>This should begin the process of updating your /usr/src directory.
>Depending on your network connection this may take from under an hour to
>several hours.
>
>*** NOTE *** you may want to do the same cvsup procedure using
>/usr/share/examples/cvsup/ports-supfile to update /usr/ports.  Just copy
>it to /etc, edit the "*default host=" line to the same as you used 
before,
>then run "cvsup -g /etc/ports-supfile".  This will update all of
>/usr/ports.

First, let me say that I did this last night and it's quite painless - 45 
minutes to CVSup (no ports) and 45 minutes to build/install.

Is it common practice to do the system *and* ports CVSup at the same time? 
Just for yucks I did the system last night and I'll try the ports tonight.

Also, there's a 

 *default release=cvs tag=

line in the example ports supfile - should I/we make that:

 *default release=cvs tag=RELENG_4_7

or is the 'cvs tag' line not relevant to the ports upgrade?

Thanks - JB

#  John Bleichert 
#  http://vonbek.dhs.org/latest.jpg

**********************************************
**********************************************

If you try to change the tag that way, you'll have a
heck of a time finding where your ports went.  ;)

Read the comments in stable-supfile (they might be in
ports-supfile also) regarding the necessity of keeping
the version line "tag=."

Yes, it's common to do system and ports at the same
time.  Not doing so might cause port builds to break
when encountering newer/older than expected versions
of build tools or other system bits.

Jud


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to