upgrading ports/packages

[Gary Kline]

On Sat, Mar 17, 2007 at 02:52:57PM -0700, Kent Stewart wrote:
> On Saturday 17 March 2007 13:55, Gary Kline wrote:
> > 	Is there a set of switches that portupgrade will use to upgrade
> > 	(from src) _only_ the ports that need rebuilding?   I'm guessing
> > 	"not" because it's either -arp or else portupgrade exits without
> > 	doing anything!
> >
> > 	My aim is to build every package just once here (700+Mhz) and
> > 	scp and pkg_add the pacakges to my slower boxen?  But even after
> > 	using pkgdb -F, the pkg_version -vIL'=" results are unchanged.
> >
> > 	thanks for any clues!
> 
> My experience is that -arp will build all of the ports from source that 
> needs building but it will (re)build all of the packages. The price for 
> using the generic "a".
> 
> On the slow machine, I wouldn't use pkg_add but portupgrade -Pa. There 
> are some ports that you can't build packages and have to build from the 
> source. So, if you have a package in /usr/ports/packages/All, 
> portupgrade will use it but if you need to build it from source, it 
> will also do that.

	I thought I saw portupgrade grabbing/recycling packages from my
	/usr/ports/packages/* collection! when pkg_verion sometimes
	reported tht a newer version was available.  For now, I'm
	resolving this by collecting the to-be-updated ports in a shell
	script and having portupgrade fetch and build a (now custom)
	binary... and package.  

	By now, I'm convinced that building everything is the best way
	since all my FBSD systems are i686's.  Be nice when the new 4.x
	version of gcc works and I can compare my own loop tests.  For 
	now, still tweaking.

	gary


> 
> Kent
> 
> >
> > 	gary
> 
> -- 
> Kent Stewart
> Richland, WA
> 
> http://www.soyandina.com/ "I am Andean project".
> http://users.owt.com/kstewart/index.html

-- 
  Gary Kline  kline at thought.org   www.thought.org  Public Service Unix