public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Mon, 17 Jul 2023 20:34:45 +0300	[thread overview]
Message-ID: <8c7d2e05-3bbf-5e12-de38-7dc96ba0cf54@gentoo.org> (raw)
In-Reply-To: <87lefebgdr.fsf@gentoo.org>


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

On 17/07/2023 19.37, Sam James wrote:
> 
> Big fan of the idea & very much in support of it. This also serves
> to give us logical groupings of packages which are closely related
> and should be bumped together.
> 
>> There was some brief discussion on IRC about how to document these
>> groupings, and two main ideas were suggested:
>>
>> - add a field to metadata.xml to specify the group by an arbitrary name.
>>   E.g. <stable-group name="..."/>
>>   Each package in the group would specify the same value of name="..."
>>
>> - maintain the groups in a separate place (similar to portage @sets).
>>
>> Can anyone think of particular advantages or disadvantages to one
>> solution versus the other? Any other (better) ideas?
>>
> 
> When we discussed this a few months ago on IRC, I also brought up a
> related point:
> 
> [2023-05-02T18:38:51+0100] <@sam_> do we want to repeat the group members in each member, or do tools need to scan for each thing?
> [2023-05-02T18:39:07+0100] <@sam_> i.e. does each member have <stable-group><pkg>...</pkg></stable-group>, or do we do <stable-group name=".../>?
> [2023-05-02T18:39:26+0100] <@arthurzam> I think each package says which groups it is part of
> [2023-05-02T18:39:44+0100] <@radhermit> I would do the latter
> [...]
> [2023-05-02T18:42:42+0100] <@radhermit> technically you could also maintain them in a separate place like metadata/groups and layer inter-group dependencies on top of that somehow in the format

If you read carefully my messages in IRC linked above, you can see I was
supporting per package metadata entry. If you read my latest post to ML,
you can see I now prefer central files. After many considerations since
then I understood my initial preference was a bad idea :)

(I'm noting it here just so folks understand the mismatch between texts
and my stance).

> I'd prefer the metadata/ at repo root idea because I can see updating
> various metadata.xmls being a nuisance.

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?

Let's wait for more input, and then we can go with defining the syntax,
rules and such...

> best,
> sam
> 

-- 
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)


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

  reply	other threads:[~2023-07-17 17:35 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 [this message]
2023-07-17 18:14     ` Ionen Wolkens
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=8c7d2e05-3bbf-5e12-de38-7dc96ba0cf54@gentoo.org \
    --to=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sam@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