public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages
Date: Fri, 21 Jun 2019 08:59:08 +0300	[thread overview]
Message-ID: <20190621085908.0f6a515900767930adea7183@gentoo.org> (raw)
In-Reply-To: <fa45adccf64ffa7b418f2d615d1c7caa94b0886a.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

On Thu, 20 Jun 2019 16:32:56 +0200 Michał Górny wrote:
> On Thu, 2019-06-20 at 09:53 -0400, Brian Evans wrote:
> > On 6/9/2019 7:39 AM, Michał Górny wrote:
> > > +Tracking of user/group usage is done through dependencies.  As long
> > > +as any installed package depends on a specific user/group package,
> > > +the respective user/group is assumed to be used.  If no package
> > > +requiring the specific user/group is left, the package manager
> > > +automatically prunes the package clearly indicating it is no longer
> > > +used.
> > 
> > You cannot know when a name is "no longer used".  An administrator could
> > have adopted a username for other purposes.
> 
> That's why we don't remove the actual user/group.  However, this is
> a valuable information to the administrator that no package is using
> the user/group in question.

So how do you propose to clean them up? Or let user systems trash
with unused uids/gids? The GLEP 81 only mensions some possible
tooling for cleanup. Is there an implementation available? I don't
see it within proposed patch sets.

This GLEP should not be accepted unless all necessary tools are
available including a cleanup tool.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-06-21  5:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 11:39 [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages Michał Górny
2019-06-13  2:21 ` Michael Orlitzky
2019-06-13  5:37   ` Michał Górny
2019-06-20 13:53 ` Brian Evans
2019-06-20 14:15   ` Michael Orlitzky
2019-06-20 14:32   ` Michał Górny
2019-06-21  5:59     ` Andrew Savchenko [this message]
2019-06-21  7:18       ` David Seifert
2019-06-21 12:02         ` Andrew Savchenko
2019-06-21 12:18           ` David Seifert
2019-06-21 13:09           ` Michał Górny
2019-06-21  8:31       ` Jaco Kroon
2019-06-21  6:03   ` Andrew Savchenko
2019-06-22 17:34   ` Andrey Utkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190621085908.0f6a515900767930adea7183@gentoo.org \
    --to=bircoph@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox