| 1 |
On Tue, 05 Jan 2021 00:16:49 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> On Mon, 2021-01-04 at 14:58 -0800, Patrick McLean wrote: |
| 5 |
> > On Mon, 4 Jan 2021 18:08:02 +0100 |
| 6 |
> > Michał Górny <mgorny@g.o> wrote: |
| 7 |
> > |
| 8 |
> > > Introduce a few variables to allow easy overrides of common user account |
| 9 |
> > > proprerties, that is: |
| 10 |
> > > |
| 11 |
> > > - ACCT_USER_<username>_SHELL |
| 12 |
> > > - ACCT_USER_<username>_HOME |
| 13 |
> > > - ACCT_USER_<username>_HOME_OWNER |
| 14 |
> > > - ACCT_USER_<username>_HOME_PERMS |
| 15 |
> > > - ACCT_USER_<username>_GROUPS |
| 16 |
> > > - ACCT_USER_<username>_GROUPS_ADD |
| 17 |
> > |
| 18 |
> > Please also add a way to override the UID/GID for the user/group. |
| 19 |
> |
| 20 |
> Damn it, and I thought I'd avoid that ;-). But do we really need it? |
| 21 |
> The eclass doesn't enforce UID/GID by default if the user exists |
| 22 |
> already, so it's a bit tangential to the original problem. |
| 23 |
> |
| 24 |
|
| 25 |
The user needs to already exist for that to be helpful. When one using |
| 26 |
automation to build/deploy large numbers of Gentoo systems, it's quite |
| 27 |
useful to have control over that sort of things. At the moment, the |
| 28 |
only way is to fork the ebuilds, which of course means they need to be |
| 29 |
kept in sync. |
Archives