Date: Thu, 15 Feb 2007 13:54:29 -0800 From: Doug Barton <dougb@FreeBSD.org> To: David Gilbert <dgilbert@dclg.ca> Cc: Jeremy Messenger <mezz7@cox.net>, freebsd ports <freebsd-ports@freebsd.org>, freebsd-hackers@freebsd.org Subject: portmaster and local ports (Was: Re: portupgrade O(n^m)?) Message-ID: <45D4D695.3090505@FreeBSD.org> In-Reply-To: <17875.33679.494974.529630@canoe.dclg.ca> References: <17875.18893.789217.224987@canoe.dclg.ca> <op.tnraowth9aq2h7@mezz.mezzweb.com> <17875.33679.494974.529630@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
David Gilbert wrote:
>>>>>> "Jeremy" == Jeremy Messenger <mezz7@cox.net> writes:
>
> Jeremy> Give ports-mgmt/portmaster a try.
>
> I just did. One flaw it has is that I have two no longer supported
> ports installed.
What do you mean by "no longer supported?"
> I want to run portmaster -a, but when it finds tund
> (and I assume it would also stop for xsysinfo), it stops.
What do you mean it stops? Are you getting, "Cannot cd to port
directory?" If so, one possible fix is to not fail if the port has an
+IGNOREME file, but rather to issue a non-fatal warning. Would that
work for you? I don't want to skip the port altogether at this point,
since even if you have an +IGNOREME file for the port you may still
want to be advised of new versions, moves, etc.
> I'd rather not just delete their package info --- it is still correct.
The other alternative, as already suggested, is to create a ports
skeleton for those two packages. For this purpose, all you'd need is a
Makefile with:
PKGNAME= foo-1.2.3
that matches what's in your +CONTENTS file. Adding the mechanism to
ignore these ports (with no skeleton) is probably a good idea for the
long run anyway, so if anyone has an idea besides what I suggested
above, speak up. :)
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45D4D695.3090505>