Date: Tue, 06 Feb 2007 08:37:15 -0500 From: Gerard Seibert <gerard@seibercom.net> To: User Questions <freebsd-questions@freebsd.org> Subject: Re: Portmanager - not working after ports change Message-ID: <20070206083609.AF2C.GERARD@seibercom.net> In-Reply-To: <20070206131927.483fe494@gumby.homeunix.com> References: <907502.10762.qm@web34404.mail.mud.yahoo.com> <20070206131927.483fe494@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday February 06, 2007 at 08:19:27 (AM) RW wrote:
> Probably it's just that someone need to patch it to change
> "sysutils/portmanager" to "ports-mgmt/portmanager" in the source.
>
> As a workaround try linking portmanager's new port directory to where
> its old one was. As there will be a MOVED entry it's probably best to
> use it with the new origin, but make sure portmanager is up-to-date
> before running it on multiple ports, it wont be able to detect a
> self-update, and it doesn't like to do that as part of a general ports'
> update.
I reported this problem around 10 am. yesterday. Sometime around 2 pm. a
patch was submitted. An updated version of 'portmanager' was in the
port's system by 4 pm. Personally, I consider that a rather quick fix.
Yes, you will have to do a regular 'make install' to get the newer
version installed. You have to do a 'make deinstall' to remove the older
version first though.
--
Gerard
Mail from '@gmail' is rejected and/or discarded here. Don't waste
your time!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070206083609.AF2C.GERARD>