Douglas Anderson schrieb am 16.12.2008 01:28:
> On Tue, Dec 16, 2008 at 9:06 AM, Daniel Pielmeier
> <> wrote:
>>> Duncan schrieb am 16.12.2008 00:47:
>>> While I'm at it, is there anything useful to display metadata.xml?  In
>>> particular, the long descriptions and use flags can be useful.  With
>>> use.desc and especially the local version thereof going deprecated, and
>>> with additional info about global flags sometimes in the metadata...
>> Regarding metadata.xml there is (besides querying Willikins on IRC)
>> emeta. Take a look at bug 248278 [1].
>> [1]
> emeta will likely become `equery meta' in the next release of
> gentoolkit, but feel free to use it from the overlay for now.
> Regarding equery, there's a "changes" option that is just waiting to
> be written. Considering udept's changleog function is about 30 lines,
> it should be trivial to do. If people are interested, I can handle
> that. It's something I would like to have, also.
> I hope to have the upgraded gentoolkit available for testing within a few 
> weeks.

Good to hear!

Besides that, is there anything similar to dep --pruneworld.

It happens to me sometimes that I forget --oneshot and packages are
added to the world file that are not intended to be there. So this
option gives an overview over packages in world that have no reverse
dependencies and thus are probably not needed. There might still be some
packages without reverse dependencies in the world file that are
intended to be there because the user wants it there, but being
presented with a list of possible unneeded packages it is more easy to
determine which are intended to be there and which are not.

For checking the reverse dependencies of single packages there is of
course "emerge -pv --depclean <atom>", but it is a tedious job to this
for every entry in the world file. I hacked something together which
runs the above command for every entry in world but this is very slow
and dep is much faster doing this check.



Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to