Gentoo Archives: gentoo-dev

From: Michael Orlitzky <mjo@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [PATCH] acct-user.eclass: don't modify existing user by default
Date: Mon, 04 Jan 2021 18:07:27
Message-Id: 89a1c171-de56-4f9e-af2a-9140d2be3552@gentoo.org
In Reply to: [gentoo-dev] Re: [PATCH] acct-user.eclass: don't modify existing user by default by James Cloos
1 On 1/4/21 11:45 AM, James Cloos wrote:
2 >>>>>> "RHJ" == Robin H Johnson <robbat2@g.o> writes:
3 >
4 > RHJ> The best I can come up with at the moment, is that any packaging should
5 > RHJ> detect if there are user modifications, and provide control to users
6 > RHJ> based on that fact.
7 >
8 > Exactly. Akin to etc-update.
9 >
10
11 We could implement this with something like an /etc/users.d directory
12 that would be populated with entries by either the admin or package
13 manager with CONFIG_PROTECT enabled. Then the system database would be
14 updated by running something like "users-update" (cf. env-update). The
15 essential problem that we need to work around is that e.g. /etc/passwd
16 is "owned" by multiple system packages.
17
18 I think this would accomplish what you and Robin are talking about, but
19 it wouldn't solve whissi's problem since it's still a Gentoo-specific
20 solution.

Replies