public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Mon, 17 Jul 2023 14:14:39 -0400	[thread overview]
Message-ID: <ZLWFDx7LrQOhR89Y@eversor> (raw)
In-Reply-To: <8c7d2e05-3bbf-5e12-de38-7dc96ba0cf54@gentoo.org>

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

On Mon, Jul 17, 2023 at 08:34:45PM +0300, Arthur Zamarin wrote:
> Hmm, I was thinking the opposite (maintaining it in parallel place to
> the package would be harder), but if you say so (and you help maintain
> huge clusters of packages so I believe you) then I think we don't have
> any good reason to go with per package metadata.xml entry?

imo seeing/setting it all in one place is simpler, ultimately it's
about managing a group (whole) and I don't think is super important
on the individual packages.

e.g.

[qt]
dev-qt/package
dev-qt/package2

Can visualize and don't have to go set this in each one of them.

fwiw repo-cd could be given a hook to grep that file, and be able
to say that a package is part of a stabilization group -- and if
nattka automatically looks at groups it'll also be hard to overlook
when filing bugs.

Regardless of approach, some kind of central file (generated or not)
would certainly be nice not to end up grepping all metadata.xml in
the tree to figure out which packages are part of a group.
-- 
ionen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-07-17 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 14:57 [gentoo-dev] Package stabilization groups Matt Turner
2023-07-16 15:15 ` Fabian Groffen
2023-07-16 15:29   ` Matt Turner
2023-07-16 18:04 ` Arthur Zamarin
2023-07-16 18:11   ` Ulrich Mueller
2023-07-16 18:13     ` Arthur Zamarin
2023-07-17 13:50   ` Matt Turner
2023-07-17 16:39     ` Arthur Zamarin
2023-07-18  3:42       ` Oskari Pirhonen
2023-07-17 16:37 ` Sam James
2023-07-17 17:34   ` Arthur Zamarin
2023-07-17 18:14     ` Ionen Wolkens [this message]
2023-07-24 13:22 ` Agostino Sarubbo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZLWFDx7LrQOhR89Y@eversor \
    --to=ionen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox