From owner-freebsd-ports@FreeBSD.ORG Wed Jun 7 18:52:55 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E364016D6A5 for ; Wed, 7 Jun 2006 17:26:34 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from centrmmtao02.cox.net (centrmmtao02.cox.net [70.168.83.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A6C043D4C for ; Wed, 7 Jun 2006 17:26:33 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by centrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060607172629.IYWT12772.centrmmtao02.cox.net@mezz.mezzweb.com>; Wed, 7 Jun 2006 13:26:29 -0400 Date: Wed, 07 Jun 2006 12:26:57 -0500 To: "Hans Lambermont" References: <4485DBF5.3070705@FreeBSD.org> <20060607121927.GA19923@leia.lambermont.dyndns.org> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20060607121927.GA19923@leia.lambermont.dyndns.org> User-Agent: Opera M2/8.54 (Linux, build 1745) Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade ideas page X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2006 18:52:55 -0000 On Wed, 07 Jun 2006 07:19:27 -0500, Hans Lambermont wrote: > Sergey Matveychuk wrote: > >> Portupgrade ideas page was created on our wiki server: >> http://wiki.freebsd.org/portupgrade >> I would like to hear your ideas, wishes and comments. > > - improved robustness : > - understand ruby/portupgrade upgrade order. Maybe restart after one > of these was upgraded too ? > - warn about UPDATING entries for ports that upgrade 'over' > (time-wise) such an entry before upgrading starts, maybe even > default to requiring a 'do continue' user action. > - be able to handle gnome and glib upgrades, basically obsoleting > gnome_upgrade.sh We already have obsolted gnome_upgrade.sh for GNOME 2.12 -> 2.14 when we have found a bug in libtool. But I understand your point of portupgrade is supposed to be able to handle that kind of issue before we obsolted gnome_upgrade.sh. > - similar for perl, maybe mention perl-after-upgrade ? > - save backout modules somewhere and add interface backout to a set of > these saved modules. > - speed : > - 'make config' default on all target ports before starting the first > build. I never have use portupgrade -m, so have no idea if it will working... Have you tried "portupgrade -m 'config-recursive'"? or "portupgrade -m 'config'"? > - 'make fetch' option on all target ports before starting the first > build. The portupgrade -F will downloading the distfile first, no build/install. But you can do 'portupgrade -F[...] ; portupgrade -a[...]' if you want to fetch first then build/install. Cheers, Mezz > - clarity : > - show a dependency graph of the entire upgrade order beforehand, also > listing the KNOBS (make.conf and pkgtools) and OPTIONS per port. > - list the ports afterwards that were newly installed during an > upgrade. > - option to show all relevant pkg-message files at the end of the > upgrade again. > > regards, > Hans Lambermont -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org