From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] New acct-* package policy
Date: Sat, 21 Dec 2019 18:32:21 +0100 [thread overview]
Message-ID: <0f3118f45820a27cf66a58d14144eb62b60733a4.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Hello, everyone.
The Council has approved removing policy part from GLEP 81 [1] which
enabled QA to establish a new easier policy for acct-* packages [2].
The most important change is that the requirement of gentoo-dev RFC is
removed. Instead, developers just take the next free UID/GID in range
499..101 and commit the packages at will. The policy recommends going
downwards from 499, and taking the same number for matching user/group
(even if it would mean leaving gaps in assignments).
Please commit and push uid-gid.txt [3] change to data/api.git *before*
your packages. This makes sure that any potential collisions are caught
as merge conflicts before they hit users. The CI also catches UID/GID
collisions.
I hope this will make migrating packages to the new system much easier.
Thanks to all the people participating in the effort.
[1] https://www.gentoo.org/glep/glep-0081.html
[2] https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies#GLEP_81_.28acct-.2A.29_package_policy
[3] https://gitweb.gentoo.org/data/api.git/tree/files/uid-gid.txt
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2019-12-21 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 17:32 Michał Górny [this message]
2020-01-06 0:36 ` [gentoo-dev] New acct-* package policy Martin Dummer
2020-01-06 0:41 ` Ralph Seichter
2020-01-06 0:46 ` Aaron Bauman
2020-01-06 7:39 ` Joonas Niilola
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=0f3118f45820a27cf66a58d14144eb62b60733a4.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev-announce@lists.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