From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)
Date: Tue, 10 Dec 2019 06:28:29 +0100 [thread overview]
Message-ID: <b931dcf838596e4d686c1544d7bc5f14ce021f92.camel@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr9ULsfB-D4navy95JTP_3nB8eD7uo8V5e7z97m4HYaaOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4101 bytes --]
On Mon, 2019-12-09 at 13:48 -0800, Alec Warner wrote:
> On Mon, Dec 9, 2019 at 12:17 AM Michał Górny <mgorny@gentoo.org> wrote:
>
> > Hello,
> >
> > I think the policies proposed in GLEP 81 [1] were overenthusiastic
> > and they don't stand collision with sad Gentoo developer reality.
> > Instead of improving the quality of resulting packages, they rather
> > hamper their adoption and cause growing frustration.
> >
> > The problems I see today are:
> >
> >
> > 1. Mailing list reviews hamper the adoption of new user packages.
> >
> > Firstly, there are a few developers who obstructively refuse to
> > communicate with others and especially to use the public mailing lists.
> > While this is a separate problem, and a problem that needs to be
> > resolved, this GLEP can't resolve it. Of course, there is no reason to
> > believe that removing review requirement will actually make them migrate
> > their packages but it's at least one obstacle out of the way.
> >
> > Secondly, even developers capable of communication find the two stage
> > request-wait-commit workflow inconvenient. At any time, there are
> > at least a few requests waiting for being committed, possibly with
> > the developers forgetting about them.
> >
> >
> > 2. Mailing list reviews don't serve their original purpose.
> >
> > The original purpose of mailing list reviews was to verify that
> > the developers use new packages correctly. For example, Michael
> > Orlitzky has found a lot of unnecessary home directories specified.
> > Of course, that works only if people submit *ebuilds* for review.
> >
> > However, at some points developers arbitrarily decided to send only
> > numbers for review. This defeats the purpose of the review in the first
> > place.
> >
> >
> > 3. Cross-distro syncing has no purpose.
> >
> > One of the original ideas was to reuse UID/GID numbers from other
> > distros when available to improve sync. However, given the collisions
> > between old Gentoo UIDs and other distros, other distros themselves,
> > non-overlapping user/group names, etc. there seems to be little reason
> > to actually do it. If we even managed some overlap, it would be minimal
> > and quasi-random.
> >
> > While other distros provide a cheap way of choosing new UID/GID, it
> > doesn't seem that many people actually use it. Then we hit pretty
> > absurd situations when someone chooses one UID/GID, somebody else tells
> > him to use the one from other distro.
> >
> >
> > 4. Assignment mechanism is not collision-prone.
> >
> > The secondary goal of mailing list reviews is to prevent UID/GID
> > collisions. Sadly, it doesn't work there either. Sometimes two people
> > request the same UID/GID, and only sometimes somebody else notices.
> > In the end, people have hard time figuring out which number is the 'next
> > free', sometimes they discover the number's been taken when somebody
> > else commits it first.
> >
> >
> > All that considered, I'd like to open discussion how we could improve
> > things.
> >
> > My proposal would be to:
> >
> > a. split the UID/GID range into 'high' (app) and 'low' (system)
> > assignments, 'high' being >=100 and 'low' <100 (matching Apache suEXEC
> > defaults),
> >
> > b. UIDs/GIDs in the 'high' range can be taken arbitrarily (recommending
> > taking highest free), while in the 'low' range must be approved by QA,
> >
> > c. no review requirement for the 'high' range, just choose your UID/GID
> > straight of uid-gid.txt and commit it.
> >
>
> What is the mechanism to keep the uid-gid.txt aligned with tree content? is
> there a CI check that says I am using the new acct-* eclasses AND I have a
> UID / GID assigned that is not matching uid-gid.txt? I see the CI has
> "ConflictingAccountIdentifiers", is this already doing this work (checking
> that the ebuild matchines uid-gid.txt), or just scanning the whole tree and
> ensuring that 2 packages don't re-use the same ID?
>
The latter.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-12-10 5:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 8:17 [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing) Michał Górny
2019-12-09 9:44 ` Ulrich Mueller
2019-12-09 10:00 ` Ulrich Mueller
2019-12-09 16:54 ` Thomas Deutschmann
2019-12-09 17:47 ` Ulrich Mueller
2019-12-09 18:02 ` Thomas Deutschmann
2019-12-09 18:48 ` Ulrich Mueller
2019-12-09 20:10 ` Thomas Deutschmann
2019-12-10 14:36 ` Michael Orlitzky
2019-12-09 21:48 ` Alec Warner
2019-12-10 5:28 ` Michał Górny [this message]
2019-12-10 5:44 ` Joonas Niilola
2019-12-10 11:47 ` Rich Freeman
2019-12-10 12:26 ` Thomas Deutschmann
2019-12-10 12:44 ` Rich Freeman
2019-12-10 13:25 ` Thomas Deutschmann
2019-12-10 13:48 ` Rich Freeman
2019-12-10 16:05 ` Joonas Niilola
2019-12-10 16:25 ` Michael Orlitzky
2019-12-10 13:34 ` Michał Górny
2019-12-10 16:13 ` Joonas Niilola
2019-12-10 16:17 ` Michał Górny
2019-12-10 14:50 ` Michael Orlitzky
2019-12-10 15:04 ` Michał Górny
2019-12-10 15:54 ` Rich Freeman
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=b931dcf838596e4d686c1544d7bc5f14ce021f92.camel@gentoo.org \
--to=mgorny@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