Date: Sat, 08 Aug 2009 20:11:23 +0100 From: Lawrence Stewart <lstewart@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: Frederique Rijsdijk <frederique@isafeelin.org>, Miroslav Lachman <000.fbsd@quip.cz>, freebsd-ports@freebsd.org Subject: Re: portmaster -x not working? Message-ID: <4A7DCDDB.3010205@freebsd.org> In-Reply-To: <4A7DC956.5010402@FreeBSD.org> References: <4A5C954C.5060507@quip.cz> <4A5C9A98.5020006@isafeelin.org> <4A5CA8CF.2070906@freebsd.org> <4A5D9FD8.3080209@isafeelin.org> <4A5E02DE.1010908@freebsd.org> <4A7DC792.2080200@freebsd.org> <4A7DC956.5010402@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > Lawrence Stewart wrote: > >> Today, I again had need of the ability to exclude multiple ports from an >> update run. It turns out your tip doesn't work with portmaster, though I >> suspect it would with portupgrade. > > For now, if you need to exclude more than one port you can check the > man page about +IGNOREME files. > Ok cool. I would definitely like to be able to specify things dynamically on a per-run basis as well though without adding +IGNOREME files. I often want to special case the exclusion of ports one time only. >> Doug, what do you think of the attached patch? > > I think it's interesting, but not quite how I would do it. I have > plans to rewrite the command line parser in order to accommodate this, > and make things easier to work with generally, so stay tuned. No problemo, will stay tuned. Cheers, Lawrence
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A7DCDDB.3010205>