• Re: [gentoo-dev] [RFC PATCH] metadata: Add gnome package stabilization

    From Sam James@21:1/5 to Florian Schmaus on Sat Jul 22 20:50:02 2023
    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).

    -----BEGIN PGP SIGNATURE-----

    iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZLwi118UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZAtXQD+PZG9+NDvzHXT8l9LLI94h4Df1s5shAMlCAWq m66EVYEA/jgsmRw4SUSmYMNzcesvW2imX57qy6eWHXJD3EIAdAsF
    =DqOh
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)