From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC PATCH] metadata: Add gnome package stabilization groups
Date: Sat, 22 Jul 2023 19:40:06 +0100 [thread overview]
Message-ID: <87bkg34wmg.fsf@gentoo.org> (raw)
In-Reply-To: <cfb65a77-f7ae-90a6-073a-ebc19664cc33@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 4188 bytes --]
Florian Schmaus <flow@gentoo.org> writes:
> [[PGP Signed Part:Undecided]]
> On 19/07/2023 18.10, Matt Turner wrote:
>> Signed-off-by: Matt Turner <mattst88@gentoo.org>
>> ---
>> Feel free to bikeshed the location, structure, file-format, etc.
>> metadata/stabilization-groups/gnome/evolution | 3 +++
>> metadata/stabilization-groups/gnome/glib | 3 +++
>> metadata/stabilization-groups/gnome/gnome-shell | 4 ++++
>> metadata/stabilization-groups/gnome/gobject-introspection | 2 ++
>> metadata/stabilization-groups/gnome/sysprof | 3 +++
>> metadata/stabilization-groups/gnome/vala | 2 ++
>> metadata/stabilization-groups/gnome/vte | 3 +++
>> 7 files changed, 20 insertions(+)
>> create mode 100644 metadata/stabilization-groups/gnome/evolution
>> create mode 100644 metadata/stabilization-groups/gnome/glib
>> create mode 100644 metadata/stabilization-groups/gnome/gnome-shell
>> create mode 100644 metadata/stabilization-groups/gnome/gobject-introspection
>> create mode 100644 metadata/stabilization-groups/gnome/sysprof
>> create mode 100644 metadata/stabilization-groups/gnome/vala
>> create mode 100644 metadata/stabilization-groups/gnome/vte
>> diff --git a/metadata/stabilization-groups/gnome/evolution
>> b/metadata/stabilization-groups/gnome/evolution
>> new file mode 100644
>> index 000000000000..21bbcf804e94
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/evolution
>> @@ -0,0 +1,3 @@
>> +gnome-extra/evolution-data-server
>> +gnome-extra/evolution-ews
>> +mail-client/evolution
>> diff --git a/metadata/stabilization-groups/gnome/glib b/metadata/stabilization-groups/gnome/glib
>> new file mode 100644
>> index 000000000000..51a5659dd725
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/glib
>> @@ -0,0 +1,3 @@
>> +dev-libs/glib
>> +dev-util/gdbus-codegen
>> +dev-util/glib-utils
>> diff --git a/metadata/stabilization-groups/gnome/gnome-shell b/metadata/stabilization-groups/gnome/gnome-shell
>> new file mode 100644
>> index 000000000000..ddf76f8f88f4
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/gnome-shell
>> @@ -0,0 +1,4 @@
>> +gnome-base/gnome-shell
>> +gnome-extra/gnome-shell-extensions
>> +gnome-extra/gnome-shell-frippery
>> +x11-wm/mutter
>> diff --git a/metadata/stabilization-groups/gnome/gobject-introspection b/metadata/stabilization-groups/gnome/gobject-introspection
>> new file mode 100644
>> index 000000000000..8baf4ae59124
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/gobject-introspection
>> @@ -0,0 +1,2 @@
>> +dev-libs/gobject-introspection
>> +dev-libs/gobject-introspection-common
>> diff --git a/metadata/stabilization-groups/gnome/sysprof b/metadata/stabilization-groups/gnome/sysprof
>> new file mode 100644
>> index 000000000000..66a338916039
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/sysprof
>> @@ -0,0 +1,3 @@
>> +dev-util/sysprof
>> +dev-util/sysprof-capture
>> +dev-util/sysprof-common
>> diff --git a/metadata/stabilization-groups/gnome/vala b/metadata/stabilization-groups/gnome/vala
>> new file mode 100644
>> index 000000000000..2e4d5a33748d
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/vala
>> @@ -0,0 +1,2 @@
>> +dev-lang/vala
>> +dev-libs/vala-common
>> diff --git a/metadata/stabilization-groups/gnome/vte b/metadata/stabilization-groups/gnome/vte
>> new file mode 100644
>> index 000000000000..ce25ab265262
>> --- /dev/null
>> +++ b/metadata/stabilization-groups/gnome/vte
>> @@ -0,0 +1,3 @@
>> +gui-libs/vte
>> +gui-libs/vte-common
>> +x11-libs/vte
>
>
> Couldn't stabilization groups be package sets? For example, instead of
>
> metadata/stabilization-groups/gnome/vte
>
> you have
>
> sets/stable-group-gnome-vte
>
> with the exact same content (may requires that :;gentoo declares a
> sets.conf).
This then ends up polluting users' list of sets, e.g. when they run
`emerge --list-sets`, or `emerge @<TAB>`, and so on.
It had occurred to me but I decided not to suggest it for this
reason. Also, these groups aren't necessarily going to be things
users should emerge directly at all (e.g. related libraries).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
prev parent reply other threads:[~2023-07-22 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 16:10 [gentoo-dev] [RFC PATCH] metadata: Add gnome package stabilization groups Matt Turner
2023-07-21 18:22 ` [gentoo-dev] " Arthur Zamarin
2023-07-24 13:58 ` Matt Turner
2023-07-22 17:08 ` [gentoo-dev] " Florian Schmaus
2023-07-22 18:40 ` Sam James [this message]
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=87bkg34wmg.fsf@gentoo.org \
--to=sam@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