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:14 99%       ` Michael 'veremitz' Everitt
  0 siblings, 0 replies; 1+ results
From: Michael 'veremitz' Everitt @ 2019-12-28 11:14 UTC (permalink / raw
  To: gentoo-dev


[-- Attachment #1.1: Type: text/plain, Size: 1031 bytes --]

On 28/12/19 11:05, Kent Fredric wrote:
> On Sat, 28 Dec 2019 10:35:09 +0100
> Fabian Groffen <grobian@gentoo.org> wrote:
>
>> Hmmm, interested to hear what kind of things you're thinking about here.
> A lot of the "Work" of filing a keyword request is modelling all the
> consequential keywordings that have to take place.
>
> If there was say, a web based UI, that:
>
> - Automatically determined which packages are ready for stabilization
>   due to all their dependencies already being stable (and maybe with
>   automatic cooldown-from-testing detection )
>
> - Automatically determined which packages can be keyworded without
>   additional work due to all their dependencies being keyworded
<snip>

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 ...


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 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 99%       ` Michael 'veremitz' Everitt

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