From owner-freebsd-questions@FreeBSD.ORG Fri Apr 9 14:40:56 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F090F16A4CE for ; Fri, 9 Apr 2004 14:40:56 -0700 (PDT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA9943D53 for ; Fri, 9 Apr 2004 14:40:56 -0700 (PDT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i39Lep8a005658; Fri, 9 Apr 2004 14:40:51 -0700 From: Kent Stewart To: freebsd-questions@freebsd.org Date: Fri, 9 Apr 2004 14:40:54 -0700 User-Agent: KMail/1.6.1 References: <4076527F.1060902@users.sourceforge.net> <200404091319.47679.kstewart@owt.com> <20040409212209.GA43745@tao.thought.org> In-Reply-To: <20040409212209.GA43745@tao.thought.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404091440.54500.kstewart@owt.com> cc: Andreas Davour cc: Gary Kline Subject: Re: Portupgrade problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2004 21:40:57 -0000 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