Re: keep ports updated

From: Kevin Oberman <oberman_at_es.net>
Date: Thu, 09 Nov 2006 07:57:45 -0800
> Date: Thu, 9 Nov 2006 13:51:37 +0100
> From: Riemer Palstra <riemer_at_palstra.com>
> Sender: owner-freebsd-current_at_freebsd.org
> 
> On Thu, Nov 09, 2006 at 03:46:24AM -0800, gahn wrote:
> > I have 6.1 installed and trying to get those ports up
> > to date. I did run "portupgrade -v" and the results show all of them
> > were "up-to-date with port". but it is not true; for example, nagios
> > is still 2.0 instead of 2.5.
> 
> Running portupgrade is good, but only half of the process :)
> 
> > how could I truely get those ports up to date as listed on freebsd.org
> > site?
> 
> You also need to get your ports tree to stay up to date, try using
> portsnap, csup or cvsup (in that order). As it probably will be the
> first time you run it, portsnap fetch, portsnap extract, and after that,
> regularly run portsnap fetch, portsnap update.

I don't know about portsnap, if you use csup (V6.1 or newer) or cvsup,
you should delete your ports tree first! (rm -rf /usr/ports/*). 

These programs keep a record of what files have been updated and their
versions and they will not know about any files already in your ports
tree but no longer in CVS. This can leave you system with orphans that
might include patch files which might cause builds to fail, or worse,
cause apps to mis-behave.

You only have to do this once. csup will take care of this from that
point on.

I don't know if the same is true of portsnap, but it may be. (Gotta try
it one of these days, but we have a local CVS mirror that works very
well, so I just have not had much incentive.)
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman_at_es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751

Received on Thu Nov 09 2006 - 14:58:03 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:02 UTC