public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Of death and prerm
Date: Wed, 30 Aug 2017 11:04:42 -0400	[thread overview]
Message-ID: <025ca0ac-dce6-7e2a-705f-5cb069c6aed7@gentoo.org> (raw)
In-Reply-To: <c8b41806-c01b-72f0-3826-6b3476a0cbe7@gentoo.org>

On 08/30/2017 10:24 AM, Michael Orlitzky wrote:
> On 08/30/2017 10:10 AM, Ian Stakenvicius wrote:
>>
>> I wonder though, per the original idea, wouldn't it make more sense to
>> allow uninstallation to continue and just very verbosely
>> warn/log/document what the package removal didn't do, so that it can
>> be done later by hand as needed?
>>
> 
> My gut feeling is "no," but who knows. Would you want --depclean to
> delete a user who owns files on your system without some prompt?

Ugh, nevermind -- my response is nonsense now that I re-read what you
asked. I think I've been waking up too early.

The downside to removing the package but not actually removing the user
is that you no longer have an accurate record of which users portage
installed for you. That list of no-longer-necessary-but-still-present
users is like a TODO list for people to keep their systems clean.
Keeping a bunch of unused system accounts -- some with shell access --
is its own risk.

Right now my /etc/passwd contains 29 lines, and I don't know which ones
I can delete. I think it's a nice feature if we can remedy that; running
--depclean would tell me which users are no longer needed, and after
I've cleaned up their files, I could userdel them and force portage to
uninstall the associated packages.



  reply	other threads:[~2017-08-30 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 20:38 [gentoo-dev] Of death and prerm Michael Orlitzky
2017-08-30  8:04 ` Alexis Ballier
2017-08-30 13:04   ` Michael Orlitzky
2017-08-30  9:25 ` Michał Górny
2017-08-30 13:15   ` Michael Orlitzky
2017-08-30 13:26     ` Ulrich Mueller
2017-08-30 13:32       ` Michael Orlitzky
2017-08-30 13:40         ` Ulrich Mueller
2017-08-30 13:46           ` Ian Stakenvicius
2017-08-30 14:04             ` Michael Orlitzky
2017-08-30 14:10               ` Ian Stakenvicius
2017-08-30 14:24                 ` Michael Orlitzky
2017-08-30 15:04                   ` Michael Orlitzky [this message]
2017-08-30 14:29             ` Ulrich Mueller
2017-08-30 14:45     ` Michał Górny

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=025ca0ac-dce6-7e2a-705f-5cb069c6aed7@gentoo.org \
    --to=mjo@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