public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arthur Zamarin <arthurzam@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, Matt Turner <mattst88@gentoo.org>,
	Sam James <sam@gentoo.org>, Tim Harder <radhermit@gentoo.org>
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Sun, 16 Jul 2023 21:13:26 +0300	[thread overview]
Message-ID: <86292db3-11ee-cda6-58c4-c6d9e5d04bb9@gentoo.org> (raw)
In-Reply-To: <uv8ejloam@gentoo.org>


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

On 16/07/2023 21.11, Ulrich Mueller wrote:
>>>>>> On Sun, 16 Jul 2023, Arthur Zamarin wrote:
> 
>> - enables an easier syntax as `pkgdev bugs @group1` to file a single bug
>> for all of them. In Gnome's case as an example, we could have "gnome1",
>> "gnome2", "gnome3", "gnome4", etc - groups standing for multiple
>> "layers/stages" of stabilizing, and then you could just file `pkgdev
>> bugs @gnome{1..4}` to file "at one click" the whole gnome stablereqs.
> 
> Can't we do the same that we do for local use flags? Namely, define them
> in metadata.xml, but collect them in one central location?

Do note that this grouping is done at "metadata repo", and not the
normal git repo where development is done. Meaning you need to manually
add the package to the central "index".

> Ulrich

-- 
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-16 18:13 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 [this message]
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
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=86292db3-11ee-cda6-58c4-c6d9e5d04bb9@gentoo.org \
    --to=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mattst88@gentoo.org \
    --cc=radhermit@gentoo.org \
    --cc=sam@gentoo.org \
    --cc=ulm@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