From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Sun, 16 Jul 2023 17:15:32 +0200 [thread overview]
Message-ID: <ZLQJlB03TlhK20Jm@gentoo.org> (raw)
In-Reply-To: <CAEdQ38HFJStXhFqhQqcz8sCWBZoT1WuJPojtDNAWu8XNQejNLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
On 16-07-2023 10:57:54 -0400, Matt Turner wrote:
> Hello,
>
> Many of us have started using `pkgdev bugs` to file stabilization
> bugs. It works well (Thanks Arthur!) and I encourage everyone to give
> it a try.
>
> Where possible, it files one stabilization bug per package. This makes
> arch testers' jobs easier and makes the task easier to automate.
>
> But sometimes we do want to stabilize packages together. For example
> major versions of x11-wm/mutter and gnome-base/gnome-shell are tied
> together. If a new mutter is stabilized without the new gnome-shell,
> the tree will still be consistent, but emerge -u @world will warn
> users that the mutter upgrade is blocked.
>
> 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?
I don't know how widespread the problem is, and how much it can be
generalised, but could you perhaps use a virtual, such that
stabilisation of the virtual means the deps must be satisfied?
Thanks,
Fabian
--
Fabian Groffen
Gentoo on a different level
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-16 15:15 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 [this message]
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
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=ZLQJlB03TlhK20Jm@gentoo.org \
--to=grobian@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