This adds a -k or --keywords option to qlist so that the keywords of installed packages can be displayed.
Created attachment 425684 [details, diff] 0001-qlist-add-k-keywords-option.patch This commit adds the option and documents it in the man page. Thanks, William
doesn't qdepends already do this ? $ qdepends -k KEYWORDS portage
(In reply to SpanKY from comment #2) > doesn't qdepends already do this ? > $ qdepends -k KEYWORDS portage Yeah, it seems `qdepends -k KEYWORDS '.*'` can be used to get KEYWORDS for all packages. However, it can also me nice to get a merged view via qlist, so that you don't have to run both commands and merge both program outputs together.
(In reply to Zac Medico from comment #3) qlist is meant more to be an extended interface between CONTENTS & the filesystem. KEYWORDS doesn't seem to fall into that. otherwise, why stop here ? why not any of the metadata keys ?
(In reply to SpanKY from comment #4) > (In reply to Zac Medico from comment #3) > > qlist is meant more to be an extended interface between CONTENTS & the > filesystem. KEYWORDS doesn't seem to fall into that. otherwise, why stop > here ? why not any of the metadata keys ? Yeah, I guess it depends on the use case. At work, we use `qlist -IvCURS` to generate a package list file for each image, and then we use diff when we want to compare the contents of any 2 images. If we have the keywords in the package list file, then diff will be able to show use which packages got stabilized from one image to the next, which some people happen to be interested in. Anyway, if you don't want to include this functionality in qlist, then I'll just have to get it from a separate call to `qdepends -k KEYWORDS '.*'`.
i think just KEYWORDS is a bit arbitrary, and if you wrap the call in python, it should be pretty trivial to coordinate the two by building a dict where the full atom is the key. although i see i need to add -S/-R flags to qdepends to make that reliable. i'll see about bringing feature/behavior parity there for the next version.
