From owner-freebsd-ports@FreeBSD.ORG Sat Jun 17 06:03:23 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 3938A16A47A for ; Sat, 17 Jun 2006 06:03:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 915AF43D48 for ; Sat, 17 Jun 2006 06:03:22 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 24989 invoked by uid 399); 17 Jun 2006 06:03:21 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 17 Jun 2006 06:03:21 -0000 Message-ID: <44939B27.8070501@FreeBSD.org> Date: Fri, 16 Jun 2006 23:03:19 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (X11/20060604) MIME-Version: 1.0 To: Hans Lambermont References: <4491F0AB.7050600@FreeBSD.org> <20060616143045.GA41923@leia.lambermont.dyndns.org> In-Reply-To: <20060616143045.GA41923@leia.lambermont.dyndns.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: New version of portmaster available for testing 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: Sat, 17 Jun 2006 06:03:23 -0000 Hans Lambermont wrote: > Doug Barton wrote: >> 3. Add -o option to replace an installed port with a new port from a >> different location (e.g., portmaster -o emulators/linux_base-fc4 >> linux_base) The second argument can also be specified as the name of >> the installed port (e.g., linux_base-8-8.0_15) > > nice, a hard-needed feature. Can you have multiple -o options in > combination with -a ? No, you'd have to do all your -o operations individually first. Anything else is too messy to try and track. > Just ran a quick test and have 2 points : > > 1) > portmaster -b -n -a > ... > ===>>> The devel/gnu-libtool port has been deleted: Has expired: devel/libtool15 is now stock and should be used instead > ===>>> Aborting update > > I think the -n should not abort. I've tried to be very conservative with the use of fail() in the script, it's only used when something is so far out of the ordinary that it really requires user attention/intervention. So, even in -n mode I'm inclined to bomb out and let the user sort things out before proceeding. > 2) > Maybe it is nice to state to what version a port will upgrade ? > So instead of : > ===>>> Launching child to update screen-4.0.2_3 > something like : > ===>>> Update screen-4.0.2_3 to 4.0.2_4 Nice, but difficult given the different ways that update_port() is called. I'll give this some thought. Doug -- This .signature sanitized for your protection