Date: Fri, 16 Jun 2006 23:03:19 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Hans Lambermont <hans@lambermont.dyndns.org> Cc: freebsd-ports@freebsd.org Subject: Re: New version of portmaster available for testing Message-ID: <44939B27.8070501@FreeBSD.org> In-Reply-To: <20060616143045.GA41923@leia.lambermont.dyndns.org> References: <4491F0AB.7050600@FreeBSD.org> <20060616143045.GA41923@leia.lambermont.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44939B27.8070501>