Portupgrade problem

Gary Kline kline at thought.org
Fri Apr 9 14:22:21 PDT 2004

On Fri, Apr 09, 2004 at 01:19:47PM -0700, Kent Stewart wrote:
> On Friday 09 April 2004 01:00 pm, Gary Kline wrote:
> > On Fri, Apr 09, 2004 at 09:14:07PM +0200, Andreas Davour wrote:
> > > On Fri, 9 Apr 2004, Andrew L. Gould wrote:
> > > > On Friday 09 April 2004 01:55 pm, Andreas Davour wrote:
> > >
> > > [snip]
> > >
> I run a cvsup of ports-all on a machine I usually use for testing. If 
> something breaks down, I have the other machines to recover it from. I 
> log everything and convert it into html using Ben Smithurst's cvsuplog. 
> Then, I upade my INDEX[-5] and INDEX.db; however, before I build the 
> new INDEX, I convert the current INDEX into a bzip2'ed file and keep 3 
> backups. A major disaster building INDEX is easily overcome by 
> unzipping one of the backups and the appropriate INDEX.

	(Wisdom personified....)

> >
> > 	When I do a portupgrade, my script runs pkgdb -F as a first
> > 	steps.  ...Just my dime's worth.
> >
> My dimes worth is that I won't run anything in a cronjob that may 
> require an answer from me. I also don't run pkgdb -F until portupgrade 
> tells me to do that. Since it updates the information when it is doing 
> upgrades, you only need to do it when it really has to be done.

	To clear things up a bit, my upgrade scripts are not cron'd.
	--Experience is a solid teacher.--  One script does basically
	a portupgrade -ia, the other simply a -a; either way I have to
	sit thru the pkgdb -F. The rest of the scripts do 
	portclean and leave a log of what needs to be upgraded.


   Gary Kline     kline at thought.org   www.thought.org     Public service Unix

More information about the freebsd-questions mailing list