| 1 |
On Wed, 2019-06-05 at 12:15 -0400, Michael Orlitzky wrote: |
| 2 |
> Should we require a mailing list review for new user/group packages? |
| 3 |
> |
| 4 |
> It's difficult to modify a user once you've settled on a UID, home |
| 5 |
> directory, and shell; so it pays to get things right the first time. |
| 6 |
|
| 7 |
Sounds like a good idea. I'll keep in mind for the next iteration |
| 8 |
of this GLEP. |
| 9 |
|
| 10 |
> The need is more apparent with fixed UIDs: if a popular package "steals" |
| 11 |
> a UID that some other package needs, then that other package is going to |
| 12 |
> be difficult or impossible to install (especially if it ultimately |
| 13 |
> depends on the popular package). |
| 14 |
> |
| 15 |
> A mailing list review could elicit a "hey, my package NEEDS that UID, |
| 16 |
> and yours doesn't care" before it's too late. |
| 17 |
|
| 18 |
I've already seen a major issue today: we have multiple packages using |
| 19 |
'git' user and requiring different setup for it (e.g. home directory). |
| 20 |
This is already a big problem, and having proper review should decrease |
| 21 |
the chance of things like this happening again. |
| 22 |
|
| 23 |
And yes, we will need to figure out a good solution once we start |
| 24 |
porting users. |
| 25 |
|
| 26 |
-- |
| 27 |
Best regards, |
| 28 |
Michał Górny |
Archives