On Wednesday 08 October 2003 11:33 am, David Bear wrote:
> I'm still trying to muddle through the loads of different ways to
> keep FreeBSD 'current' -- meaning, safely patched, aka RELENG_5_1
> (for me)
> As I conceptualize the operations there are two levels of 'patching',
> 1) the kernel and base system
> 2) then all the ports that I may have installed
> I've read the cvsup docs and can see how to update both the kernel
> source and ports.  But the problem I see is the ports.  After the
> ports collection has cvsupdated, I would still need to do a make
> install for each port I have previous installed, correct?  (or, more
> appropriately, make deinstall, the cvsup the ports, then make
> install) Is this making things more difficult?  Seems there really
> should be a cleaner way to keep things updated.
> I've heard reference to a portupgrade package, but can't find any
> details on how and what it really does-- and how well it plays with
> cvsupdate.

Nothing updates your ports for you automaticaly. Nothing updates INDEX-5 
and INDEX.db everytime you cvsup ports-all. INDEX-5 is currently 7 
weeks old and if you cvsup ports-all and use the INDEX that it 
provides, you have a truly ancient INDEX-5. The frequency of upgrade 
isn't going to change and so you are expected to rebuild INDEX-5 and 
INDEX.db everytime you cvsup the ports. I prefer to

cd /usr/ports
make index
portsdb -u

> The other rotten thing here is that cvsupdate requires modula-3 --
> and portupgrade requires ruby...  It would really be nice if all this
> were done in the most perfect language, python;-)

The philosophy is probably some thing like "If you don't like what some 
one else has done, write your own."   If you don't want to do that, 
then learn to live with what someone else has done :).


> looking for some advice.. thx.

Kent Stewart
Richland, WA


[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to