Date: Mon, 03 Aug 2009 12:11:08 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Jeremy Messenger <mezz@FreeBSD.org>, ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports MOVED UPDATING ports/Mk bsd.autotools.mk ports/accessibility/atk Makefile ports/accessibility/gnome-mag Makefile ports/accessibility/kdeaccessibility Makefile ports/archivers/kbackup Makefile ports/archivers/kio_p7zip ... Message-ID: <4A77364C.2060702@FreeBSD.org> In-Reply-To: <20090803160223.GB31733@titania.njm.me.uk> References: <200908021936.n72JaYSD075693@repoman.freebsd.org> <20090803160223.GB31733@titania.njm.me.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
N.J. Mann wrote:
> In message <200908021936.n72JaYSD075693@repoman.freebsd.org>,
> Jeremy Messenger (mezz@FreeBSD.org) wrote:
>> mezz 2009-08-02 19:36:34 UTC
>>
>> FreeBSD ports repository
>>
>> Modified files:
>> . MOVED UPDATING
> [...]
>
> Is the syntax for portmaster in UPDATING correct?
It was not, but I just fixed it:
portmaster -o devel/libtool22 devel/libtool15
portmaster -o devel/libltdl22 devel/libltdl15
At some future date I will update the command line parser to handle
globs for the second argument to -o.
> When I tried
>
> portmaster -o devel/libtool22 libtool-1.5.26
>
> it worked.
Yes, specifying the full name of the port directory in /var/db/pkg
will work, but it's hard to write an UPDATING entry that easily
summarizes that problem since users may be updating from versions
older than the most recent one.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A77364C.2060702>