On Sun, Nov 28, 2021 at 3:26 PM William Hubbs <willi...@gentoo.org> wrote: > > On Sun, Nov 28, 2021 at 02:57:39PM -0500, Michael Orlitzky wrote: > > On 2021-11-28 11:06:36, Ulrich Mueller wrote: > > > > > > While the rationale for static allocation that made it into GLEP 81 [1] > > > is rather weak, several people had argued in favour of it on the mailing > > > list [2]. > > > > > > > We don't even do static allocation. The UIDs and GIDs in the ebuilds > > are suggestions, meant to benefit the people who will benefit from > > them, and be ignored by everyone else. > > > > There are a few exceptional cases where a user or group needs a > > specific identifier; but those were always statically allocated and > > nothing has changed in that regard. > > Doesn't the emerge fail if a different user with ACCT_USER_ID already exists > on > the system (unless ACCT_USER_ID is set to -1, which is forbidden by qa > policy)?
Not by default. If the eclass finds that ACCT_USER_ID is already taken, it will allow useradd to assign a different one. This behavior can be overridden by ebuilds (or a user) by setting ACCT_USER_ENFORCE_ID.