Gentoo Archives: gentoo-dev

From: Mike Gilbert <floppym@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Changes made by acct-* ebuilds
Date: Fri, 14 Feb 2020 03:37:24
Message-Id: CAJ0EP433ihEchVDhDUMReHpHLngMweuFw3OyNTVKb6-3S20w9Q@mail.gmail.com
In Reply to: [gentoo-dev] Changes made by acct-* ebuilds by Michael 'veremitz' Everitt
On Thu, Feb 13, 2020 at 6:24 PM Michael 'veremitz' Everitt <
gentoo@×××××××.xyz> wrote:

> On 13/02/20 16:17, Mike Gilbert wrote: > > On Wed, Feb 12, 2020 at 8:32 PM Thomas Deutschmann <whissi@g.o> > wrote: > >> In short: It was a very bad decision that acct-* stuff is *changing* > >> existing stuff. This must be turned of *by default*. Maybe provide a > >> setting a user can put into make.conf to opt into current, still new, > >> behavior but by default, a package should never ever make changes to > >> *existing* user (unless it knows for sure it was the only source > >> creating that user and nothing was changed since creation which isn't > >> easy to track). > > I think it would make sense to add some eclass variables that would > > turn user.eclass functions into no-ops. > > > > I don't agree that this should be happen by default. I suspect the > > majority of users do not wish to manage system users/groups > > themselves. > > > I would suggest anyone competent enough to build a kernel from scratch > (genkernel users, I'm ignoring you) should be equally at-home managing > system users and groups and associated permissions? Or am I perhaps > overestimating the average Genbuntu users here ... >,< > > I said nothing of capability. Most people don’t care to micromanage > accounts.