Date: Sun, 27 Jan 2008 07:25:25 +0300 From: Yar Tikhiy <yar@comp.chem.msu.su> To: dougb@FreeBSD.org Cc: freebsd-ports-bugs@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/120002: portmaster won't show port's available version Message-ID: <20080127042525.GE49535@comp.chem.msu.su> In-Reply-To: <200801261612.m0QGCvCp094103@freefall.freebsd.org> References: <200801261612.m0QGCvCp094103@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 26, 2008 at 04:12:57PM +0000, dougb@FreeBSD.org wrote:
>
> It is expected that if the user asks to update a port, that they
> intend to actually update the port. The -L option exists to list
> which ports are up to date, and which need updating. There is also
> an alias suggested in the man page which will give you a concise
> summary of only what is not up to date.
Did you mean this one?
portmaster -L |
egrep -B1 '(ew|ort) version|Aborting|installed|dependencies|
IGNORE|marked|Reason:|MOVED' | grep -v '^--'
The command looks really hairy. The egrep is there just to fight
inconvenient output from portmaster. Perhaps a cleaner way is to
implement the functionality in portmaster itself.
Merely printing the version available from /usr/ports along with
the version installed would make updating an individual port much
more convenient. E.g.:
===>>> Update portmaster-2.0 to portmaster-2.1? [n]
I'll appreciate greatly if you consider adding this featurette to
portmaster.
Thanks a lot, portmaster does an excellent job for me in most cases.
--
Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080127042525.GE49535>