From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages
Date: Wed, 12 Jun 2019 22:21:17 -0400 [thread overview]
Message-ID: <0e79c92e-8de0-5695-961b-98cbe097c62e@gentoo.org> (raw)
In-Reply-To: <20190609113955.19208-1-mgorny@gentoo.org>
On 6/9/19 7:39 AM, Michał Górny wrote:
>
> +
> +All new users and groups must have unique UIDs/GIDs assigned
> +by developers. The developer adding them is responsible for checking
> +for collisions.
>
> ...
>
> +All user and group packages must define preferred fixed UIDs/GIDs,
> +and they must be unique within the repository. The packages should
> +indicate whether the value needs to be strictly enforced, or whether
> +another UID/GID is acceptable when the user exists already or requested
> +UID/GID is taken.
> +
Maybe we should loosen this in the case of enforced UIDs. If two
user-packages truly do require the same fixed UID (for whatever godawful
reason), then obviously they can't be installed on the same machine, but
we could otherwise support both in the repository.
I don't want to encourage people to add such badly-written software to
the repo, but the alternative is also pretty ugly: if we require the
UIDs to be unique, and if two packages require the same enforced UID,
then whoever commits to ::gentoo first will prevent the other guy from
adding his package later on.
next prev parent reply other threads:[~2019-06-13 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 11:39 [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages Michał Górny
2019-06-13 2:21 ` Michael Orlitzky [this message]
2019-06-13 5:37 ` Michał Górny
2019-06-20 13:53 ` Brian Evans
2019-06-20 14:15 ` Michael Orlitzky
2019-06-20 14:32 ` Michał Górny
2019-06-21 5:59 ` Andrew Savchenko
2019-06-21 7:18 ` David Seifert
2019-06-21 12:02 ` Andrew Savchenko
2019-06-21 12:18 ` David Seifert
2019-06-21 13:09 ` Michał Górny
2019-06-21 8:31 ` Jaco Kroon
2019-06-21 6:03 ` Andrew Savchenko
2019-06-22 17:34 ` Andrey Utkin
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=0e79c92e-8de0-5695-961b-98cbe097c62e@gentoo.org \
--to=mjo@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