From owner-freebsd-ports@FreeBSD.ORG  Wed Mar  8 20:00:21 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: 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 20D8316A420
	for <ports@freebsd.org>; Wed,  8 Mar 2006 20:00:21 +0000 (GMT)
	(envelope-from pauls@utdallas.edu)
Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 853D843D55
	for <ports@freebsd.org>; Wed,  8 Mar 2006 20:00:20 +0000 (GMT)
	(envelope-from pauls@utdallas.edu)
Received: from [10.110.3.244] (dy003244.utdallas.edu [10.110.3.244])
	by smtp1.utdallas.edu (Postfix) with ESMTP id BEFC8388C9D
	for <ports@freebsd.org>; Wed,  8 Mar 2006 14:00:19 -0600 (CST)
Date: Wed, 08 Mar 2006 14:00:19 -0600
From: Paul Schmehl <pauls@utdallas.edu>
To: ports@freebsd.org
Message-ID: <65F8D6A1C5A07B2BF1E173BA@[10.110.3.244]>
X-Mailer: Mulberry/4.0.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 
Subject: portupgrade and gnome
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, 08 Mar 2006 20:00:21 -0000

Is there any way that portupgrade could be made "smart" enough to not 
upgrade the gnome ports?  Since you have to download and run the upgrade 
script (and why isn't that part of the ports anyway?), it doesn't make a 
great deal of sense to run portupgrade and then run the gnome upgrade 
script, yet it's impossible to tell from portupgrade (when it's running) 
what are gnome dependencies and what are not.

Seems like a lot of duplication of effort could be easily fixed by either 
downloading and calling the script (and exiting portupgrade?) or simply 
ignoring any "gnome" ports.

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/