Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jul 2009 19:39:22 -0700 (PDT)
From:      Doug Barton <dougb@FreeBSD.org>
To:        Ben Morrow <ben@morrow.me.uk>
Cc:        freebsd-stable@freebsd.org
Subject:   portmaster -s text (Was: Re: HEADS-UP: Shared Library Versions bumped)
Message-ID:  <alpine.BSF.2.00.0907271933580.43191@qbhto.arg>
In-Reply-To: <20090723011246.GA29465@osiris.mauzo.dyndns.org>
References:  <1248027417.14210.110.camel@neo.cse.buffalo.edu> <58F0204B-ECE6-479A-AAC2-7868E71ABB43@exscape.org> <367b2c980907200729s57eafbbfw83c8ae5a94f41ffc@mail.gmail.com> <4A6628F0.6080802@mail.zedat.fu-berlin.de> <20090721215201.GA61999@troutmask.apl.washington.edu> <1248277420.8644.70.camel@localhost> <20090722193033.GA83848@zim.MIT.EDU> <20090723011246.GA29465@osiris.mauzo.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Jul 2009, Ben Morrow wrote:

> The problem with that is if you install pkg A deliberately, but it then
> later becomes a dependancy of pkg B. If you remove pkg B (because it's
> no longer needed) there is then no evidence that pkg A was installed on
> purpose, rather than incidentally. portmaster -s will offer to remove
> it, and if you refuse it will offer to remove the empty +REQUIRED_BY,
> effectively promoting it to a 'manually installed' pkg again, though
> it's perhaps not entirely clear from the question that that is what the
> effect will be.

Thanks for pointing this out. Can you suggest an alternative message? 
Other than the mundane reason the current message says what it does 
because I sometimes prefer to leave the empty file there so that when I go 
back through at a later date I can re-evaluate the choice.

> This would be easy to solve in general by maintaining a 'world' package,
> or some such, that had dependencies on everything installed explicitly;
> but that would require modifying all the pkg and port installation tools
> (probably including bsd.port.mk itself) to support that convention.

This sort of mechanism has been suggested before, but the problem you 
described (ports installed "on purpose" becoming a dependency of something 
else) is not an easy one to solve.

Doug

-- 

     This .signature sanitized for your protection




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0907271933580.43191>