From owner-freebsd-ports@FreeBSD.ORG  Wed Jun  7 14:03:43 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 1E18316C35E
	for <freebsd-ports@freebsd.org>; Wed,  7 Jun 2006 12:19:29 +0000 (UTC)
	(envelope-from hans@lambermont.dyndns.org)
Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.93.47.245])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A6A0D43D48
	for <freebsd-ports@freebsd.org>; Wed,  7 Jun 2006 12:19:28 +0000 (GMT)
	(envelope-from hans@lambermont.dyndns.org)
Received: by lambermont.dyndns.org (Postfix, from userid 1001)
	id 184EE22E678; Wed,  7 Jun 2006 14:19:27 +0200 (CEST)
Date: Wed, 7 Jun 2006 14:19:27 +0200
To: freebsd-ports@freebsd.org
Message-ID: <20060607121927.GA19923@leia.lambermont.dyndns.org>
References: <4485DBF5.3070705@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4485DBF5.3070705@FreeBSD.org>
User-Agent: Mutt/1.4.2.1i
From: hans@lambermont.dyndns.org (Hans Lambermont)
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2006 14:03:46 -0000

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