Date: Wed, 29 Jul 2009 11:48:33 -0700 From: Doug Barton <dougb@FreeBSD.org> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: portmaster -R (Was: Re: HEADS-UP: Shared Library Versions bumped...) Message-ID: <4A709981.80600@FreeBSD.org> In-Reply-To: <20090729170601.GA2841@tafi.alm.flutnet.org> References: <1248027417.14210.110.camel@neo.cse.buffalo.edu> <200907232335.54973.mel.flynn%2Bfbsd.current@mailing.thruhere.net> <4A6FF5FA.5010904@FreeBSD.org> <200907282342.25038.mel.flynn%2Bfbsd.current@mailing.thruhere.net> <4A707534.8000808@FreeBSD.org> <20090729170601.GA2841@tafi.alm.flutnet.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alson van der Meulen wrote:
> * Doug Barton <dougb@FreeBSD.org> [2009-07-29 18:13]:
>> Mel Flynn wrote:
>>> Gotcha. Is there a reason the flags are removed if the options are not "-r or
>>> -f"?
>> Yes, so we don't have stale flags sitting around forever to confuse
>> future runs.
>
> I have been bitten by this in the past. A run of portmaster -r
> some-lib-that-half-of-my-ports-depend-on aborted because of a shared
> library error in a dependency which was not recompiled before the
> dependent port. I recompiled the dependency with a manual portmaster
> $portname, after this portmaster -r had to start all over. I didn't
> expect portmaster to clear the PM_DONE flags during non-resumable
> operations like rebuilding a single port (and the manpage contains very
> little information about -R). My workaround is to use portupgrade for
> these manual fixes.
Yes, I've been considering that exact scenario since atm I'm
rebuilding all my ports with -afR.
How about this? When the user has -[rf] but not -R, and there are flag
files present, ask if they should be cleared before beginning to do
anything. Otherwise (no -[rf]) ignore them. Sound good?
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A709981.80600>