public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] Keywordreqs and slacking arch teams
  @ 2019-12-28 11:27 99%         ` Kent Fredric
  0 siblings, 0 replies; 1+ results
From: Kent Fredric @ 2019-12-28 11:27 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

On Sat, 28 Dec 2019 11:14:15 +0000
Michael 'veremitz' Everitt <gentoo@veremit.xyz> 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.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2019-12-28  7:09     [gentoo-dev] Keywordreqs and slacking arch teams Michał Górny
2019-12-28  9:27     ` Kent Fredric
2019-12-28  9:35       ` Fabian Groffen
2019-12-28 11:05         ` Kent Fredric
2019-12-28 11:14           ` Michael 'veremitz' Everitt
2019-12-28 11:27 99%         ` Kent Fredric

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox