[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: one for the wishlist
> On Wed, Aug 10, 2011 at 11:56 PM, Joerg Sonnenberger
> <joerg%britannica.bec.de@localhost> wrote:
>> On Wed, Aug 10, 2011 at 11:50:47PM +0200, Jörn Clausen wrote:
>>> The reason is, that pkg_info, lintpkgsrc and other tools provide a
>>> great overview of the current status of your local pkgsrc
>>> installation, but not about its history. When testing a package and
>>> removing it later, I find it hard to clean up all dependencies that
>>> are no longer used.
> Being a leaf package (even in the sense of pkg_leaves, i.e. "pkg_info
> -u" already removed from the list) does not mean it is not used
If you really want to mark packages as "I need them! Do not remove!"
remove marker "automatic" from such packages using either pkg_admin or nih.
pkg_admin unset automatic gmake zip
nih mark -u gmake zip
> I just tried pkg_leaves on my set of installed packages, and
> it reported gmake, zip and a bunch of libraries that need to be
> reinstalled with the next package or at the next update of packages
> that have a build dependency on them.
"make depends" marks dependencies (including build time ones) as
"installed as a dependency", i.e. pkg_add -A is used for this. This is
why build tools become leaf packages installed "as a dependency". This
is why pkg_leaves tries to remove them. NIH works the same way.
> Those are packages I don't want to remove. And it can't tell the
> reason why a leaf package is there, that information is lost.
See above. You probably built packages using "bmake ...".
Best regards, Aleksey Cheusov.
Main Index |
Thread Index |