From: Michael Orlitzky <mjo@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, 5 Jun 2019 12:15:09 -0400 [thread overview]
Message-ID: <ef8dc425-568f-b38b-ed73-e138ab0ec9ca@gentoo.org> (raw)
In-Reply-To: <20190605091839.17396-1-mgorny@gentoo.org>
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.
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.
next prev parent reply other threads:[~2019-06-05 16:15 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 [this message]
2019-06-05 16:29 ` Michał Górny
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=ef8dc425-568f-b38b-ed73-e138ab0ec9ca@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