Date: Wed, 7 Jun 2006 14:19:27 +0200 From: hans@lambermont.dyndns.org (Hans Lambermont) To: freebsd-ports@freebsd.org Subject: Re: portupgrade ideas page Message-ID: <20060607121927.GA19923@leia.lambermont.dyndns.org> In-Reply-To: <4485DBF5.3070705@FreeBSD.org> References: <4485DBF5.3070705@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 - 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. - 'make fetch' option on all target ports before starting the first build. - 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060607121927.GA19923>