From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 777D01382C5 for ; Mon, 4 Jan 2021 18:20:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 89F11E09E9; Mon, 4 Jan 2021 18:20:55 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4C78BE099C for ; Mon, 4 Jan 2021 18:20:55 +0000 (UTC) Message-ID: Subject: Re: [gentoo-dev] Re: [PATCH] acct-user.eclass: don't modify existing user by default From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Mon, 04 Jan 2021 19:20:49 +0100 In-Reply-To: <89a1c171-de56-4f9e-af2a-9140d2be3552@gentoo.org> References: <20210104013558.20072-1-whissi@gentoo.org> <89a1c171-de56-4f9e-af2a-9140d2be3552@gentoo.org> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 7e7da5f1-14eb-4922-90c6-e1f013eafeb5 X-Archives-Hash: 1cb87c7f7106cbc3b58029c2e0f6e98a On Mon, 2021-01-04 at 13:07 -0500, Michael Orlitzky wrote: > On 1/4/21 11:45 AM, James Cloos wrote: > > > > > > > "RHJ" == Robin H Johnson writes: > > > > RHJ> The best I can come up with at the moment, is that any packaging should > > RHJ> detect if there are user modifications, and provide control to users > > RHJ> based on that fact. > > > > Exactly. Akin to etc-update. > > > > We could implement this with something like an /etc/users.d directory > that would be populated with entries by either the admin or package > manager with CONFIG_PROTECT enabled. Then the system database would be > updated by running something like "users-update" (cf. env-update). The > essential problem that we need to work around is that e.g. /etc/passwd > is "owned" by multiple system packages. Most importantly, it doesn't resolve the core issue of 'we need to update home before merging reverse dependencies'. -- Best regards, Michał Górny