Date: Fri, 9 Apr 2004 14:40:54 -0700 From: Kent Stewart <kstewart@owt.com> To: freebsd-questions@freebsd.org Cc: Gary Kline <kline@thought.org> Subject: Re: Portupgrade problem Message-ID: <200404091440.54500.kstewart@owt.com> In-Reply-To: <20040409212209.GA43745@tao.thought.org> References: <4076527F.1060902@users.sourceforge.net> <200404091319.47679.kstewart@owt.com> <20040409212209.GA43745@tao.thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 09 April 2004 02:22 pm, Gary Kline wrote: > 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] > > 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. > One of the things I don't log is the ports that need to be updated after I have new INDEX* files. That made redoing things after the glib-2.4.0 update more difficult. The process I used had built something out of order and had a port that still wanted libglib-2.0.so.200 instead of the new .so.400. If I had the log, I could have just force rebuilt everything instead of letting ruby (an AMD 2400+) spend 13 hours doing a -rf glib. When I get back from dinner, I think I will create a script to log the portversion -c. Then, I will have a list of ports that need to be updated. Hindsight after a problem is a good teacher. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404091440.54500.kstewart>