Well, this configuration is reasonable, I am for the change
On 18/07/2023 10.42, Зураб Квачадзе wrote:
> How do we handle this case, then.
> Imagine we have a leaf package acct-user/foo, which has a reserved UID
> of 123. It gets last rited and its entry is removed from uid-gid.txt.
Nobody is proposing that the uid-gid.txt entry is removed. Ideally, it
would be marked as 'historical', together with the date it went historical.
> After a while appears a new package acct-user/bar, which takes the 123
> UID. Then a user, say Bob, updates their system, which haven't been
> updated for some time. What if they still have acct-user/foo, when > acct-user/bar with the same UID is installed?
If a UID/GID is in use, then acct-*.eclass will find the next suitable
ID (unless, e.g. ACCT_USER_ENFORCE_ID is set, we is usually not the case).
- Flow