From: "Ulrich Müller" <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The meaning of attributes in repositories.xml?
Date: Fri, 28 Mar 2025 12:59:06 +0100 [thread overview]
Message-ID: <uecyh74dx@gentoo.org> (raw)
In-Reply-To: <e1b1782524de579077d89b862a5302d60656e20f.camel@gentoo.org> ("Michał Górny"'s message of "Fri, 28 Mar 2025 05:27:40 +0100")
[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]
>>>>> On Fri, 28 Mar 2025, Michał Górny wrote:
> I've looked at our repositories.xml and the quality/status attributes
> don't seem to be used very meaningfully.
> That is, by quality:
> core: gentoo [official]
> stable: opentransactions (?) [official (?!)]
> testing: hyprland-overlay, moexiami [both unofficial]
> experimental: everything else
> graveyard: unused
> By status:
> official: ago, alexxy, anarchy, andrey_utkin, cj-overlay, dilfridge,
> emacs, EmilienMottet, fordfrog, gentoo, gnome, gnustep, graaff, guru,
> haskell, java, jmbsvicetto, kde, libressl, maekke, masterlay, mschiff,
> multilib-portage, musl, mysql, opentransactions, pentoo, pinkbyte,
> qemu-init, qt, R_Overlay, rich0, riscv, rnp, ruby, science, sping,
> swegener, tex-overlay, toolchain, ukui, ulm, vGist, voyageur, x11
> unofficial: everything else
> Which brings the significant question: are these attributes in any way
> meaningful? Is there a point in keeping them at all? Should we set
> some ground rules and make them used consistently?
> Of them all, only "core" makes sense right now. "stable" and "testing"
> are used only by random user overlays, with no apparent features.
> Similarly, "official" is used by a mix of developer and ex-developer
> repositories, developer and user project repositories, and a bunch of
> user repositories with no clearly distinct features.
I've recently looked at these too, in the context of EAPI deprecation
(GLEP 83). Basically, which repositories should we consider before
dropping support for an old EAPI from package managers?
For example, one could consider all "official" repositories. But then
I looked at some of them and found quite a few that are essentially
unmaintained (e.g. because the developer retired). Also, the "quality"
attribute didn't make sense to me at all.
One idea could be to merge these into a single status attribute, and
maybe salvage the "core" value. That is:
- core: Only the Gentoo repository (for the time being)
- official: Repositories maintained by a project or a developer
(maybe opt-in or opt-out, i.e. allow devs to have unofficial
repositories?)
- unofficial: everything else
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2025-03-28 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 4:27 [gentoo-dev] The meaning of attributes in repositories.xml? Michał Górny
2025-03-28 8:15 ` [gentoo-dev] " Anna Vyalkova
2025-03-28 8:59 ` Ionen Wolkens
2025-03-28 8:23 ` Duncan
2025-03-28 13:04 ` Michał Górny
2025-03-28 16:31 ` Duncan
2025-03-30 14:37 ` Gerion Entrup
2025-03-28 11:59 ` Ulrich Müller [this message]
2025-03-28 12:57 ` [gentoo-dev] " Michał Górny
2025-03-28 16:51 ` Ulrich Müller
2025-03-28 17:19 ` Michał Górny
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=uecyh74dx@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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