From owner-freebsd-ports@FreeBSD.ORG  Wed Jun 30 05:15:14 2004
Return-Path: <owner-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 B13A316A4CE
	for <ports@freebsd.org>; Wed, 30 Jun 2004 05:15:14 +0000 (GMT)
Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.251])
	by mx1.FreeBSD.org (Postfix) with SMTP id A256B43D4C
	for <ports@freebsd.org>; Wed, 30 Jun 2004 05:15:14 +0000 (GMT)
	(envelope-from roop.nanuwa@gmail.com)
Received: by mproxy.gmail.com with SMTP id w29so1564782cwb
        for <ports@freebsd.org>; Tue, 29 Jun 2004 22:14:59 -0700 (PDT)
Received: by 10.11.118.71 with SMTP id q71mr1731737cwc;
        Tue, 29 Jun 2004 22:14:59 -0700 (PDT)
Message-ID: <75f3f70504062922141aa61b5e@mail.gmail.com>
Date: Tue, 29 Jun 2004 22:14:53 -0700
From: Roop Nanuwa <roop.nanuwa@gmail.com>
To: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu>
In-Reply-To: <1088569502.83913.35.camel@rushlight.kf8nh.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <75f3f70504062921126b075a65@mail.gmail.com>
	<1088569502.83913.35.camel@rushlight.kf8nh.com>
cc: ports@freebsd.org
Subject: Re: FreeBSD Port: portupgrade-20040529
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
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, 30 Jun 2004 05:15:14 -0000

On Wed, 30 Jun 2004 00:25:03 -0400, Brandon S. Allbery KF8NH
<allbery@ece.cmu.edu> wrote:
> 
> Actually, it looks to me like portinstall/portupgrade just issues a
> "make install" for the highest level dependency it can and lets the
> usual bsd.ports.mk port dependency stuff do all the work, so it doesn't
> have control over what happens in between those builds.  I suspect
> changing that would require making portinstall/portupgrade a lot smarter
> (and then potentially having to update them every time bsd.ports.mk
> changes, since it can no longer let bsd.ports.mk do the heavy lifting).

I was worried that would be the case. I looked over the feature set and there
was a line about how the portupgrade tools can follow dependency trees so I
thought there might be a chance it did handle things a bit "smarter".

--roop