Michael Orlitzky <mjo <at> gentoo.org> writes:
> portageq --maintainer-email can do it, but it only checks your installed > overlays. I have htop install, and 'idl0r' is the maintainer 'portageq --maintainer-email idl0r' comes back empty as with any number of dev-handles listed in metadata for installed packages. when ran as root. It throws errors when run as a user. correct syntax ?? portageq is not documented in the man page for portage ? is portageq -h the extent of available docs? I did find this scant info in the wiki:: https://wiki.gentoo.org/wiki/Portage#portageq and a listing of 'portageq -h' and a wee bit more here:: https://wiki.gentoo.org/wiki/Portageq I was hoping for a separate code/script I could hack on. I doubt seriously, (my) hacks to portage are going to be welcome... Anyway that's a neat tool and close, but I'm not sure how to wise patching portage is to extend the features. A non-core package would be fine. I'll look at the portageq code on github and see if I can make a stand alone script or q-applet to extend this metadata query. Packages I already have installed are not the issue. What I want is a quick and convenient tool to 'periscope' into all the gentoo published work a dev might have so as to better understand the focus(es) of their work and common interests. With blueness, it's dirt simple:: https://wiki.gentoo.org/wiki/User:Blueness && https://dev.gentoo.org/~blueness/ But this basic information would be very nice if a tool parsed out the basics so each and every dev does not have to do this. I'm trying to 'not reinvent the wheel' but it is a great help, particularly for the product devs that are into the same sorts of things as I am. (ultrabug) for example. thx, James
