On Sat, 28 Dec 2019 11:14:15 +0000 Michael 'veremitz' Everitt wrote: > I know I'm gonna be shot down in flames, because $heresy, but here is where > a package 'database' would actually work quite well, because you can > trivially create a query that pulls this data out, and sorts it by package > category or maintainer or whatever you like .. > > Ok, let the flamewars begin ... There's no real problem with a package database, however, the real limitation is in the ebuild source format, which ultimately means any such database needs a lot of bash-sourcing hell to simply stay up-to-date ( any time an eclass changes, the interpretation of every ebuild that uses it also changes, necessitating some pretty fun(1) code ) And that winds you up fighting with portage internals. So simply, in order for somebody like me to actually implement such a thing, a precursory step is to rewrite enough portage to do just that. But I haven't (yet) gotten around to that. 1: Not actually fun.