From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2] glep-xxxx: User and group management via dedicated packages
Date: Wed, 05 Jun 2019 18:29:33 +0200 [thread overview]
Message-ID: <9cbfa8e589153ec658ba54b44079be2d6beecbd2.camel@gentoo.org> (raw)
In-Reply-To: <ef8dc425-568f-b38b-ed73-e138ab0ec9ca@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Wed, 2019-06-05 at 12:15 -0400, Michael Orlitzky wrote:
> Should we require a mailing list review for new user/group packages?
>
> It's difficult to modify a user once you've settled on a UID, home
> directory, and shell; so it pays to get things right the first time.
Sounds like a good idea. I'll keep in mind for the next iteration
of this GLEP.
> The need is more apparent with fixed UIDs: if a popular package "steals"
> a UID that some other package needs, then that other package is going to
> be difficult or impossible to install (especially if it ultimately
> depends on the popular package).
>
> A mailing list review could elicit a "hey, my package NEEDS that UID,
> and yours doesn't care" before it's too late.
I've already seen a major issue today: we have multiple packages using
'git' user and requiring different setup for it (e.g. home directory).
This is already a big problem, and having proper review should decrease
the chance of things like this happening again.
And yes, we will need to figure out a good solution once we start
porting users.
--
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-06-05 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 9:18 [gentoo-dev] [PATCH v2] glep-xxxx: User and group management via dedicated packages Michał Górny
2019-06-05 16:15 ` Michael Orlitzky
2019-06-05 16:29 ` Michał Górny [this message]
2019-06-05 16:43 ` Ulrich Mueller
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=9cbfa8e589153ec658ba54b44079be2d6beecbd2.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