#224813 debfoster should not purge packages per default

Package:
debfoster
Source:
debfoster
Description:
Install only wanted Debian packages
Submitter:
Christoph Berg
Date:
2024-11-24 08:15:02 UTC
Severity:
wishlist
Tags:
#224813#5
Date:
2003-12-22 14:11:58 UTC
From:
To:
Per default, debfoster calls "apt-get --purge remove" to remove unwanted
packages. I think that is contrary to the Debian way of not removing
configuration files unless the user asks for it. Furthermore, the fact
that the command is called "remove" but does invoke --purge is
misleading. Since "prune" potentially removes (purges) lots of packages,
chances are high that valuable configuration files are lost.

I suggest the following:
* make "RemoveCmd = apt-get remove" the default in /etc/debfoster.conf
* (optionally) introduce upper case versions of 'n' and 'p' that call
  "PurgeCmd" (that defaults to the previous default for "RemoveCmd")

To make things more verbose, it might make sense to introduce 'k'eep =
yes, 'r'emove = no, 'R'remove = purge.

(Yes I can change the setting in /etc/debfoster.conf, but the default is
too dangerous to stay that way IMHO.)
#224813#10
Date:
2003-12-22 19:45:23 UTC
From:
To:
tag 224813 +patch
thanks

This is implemented in the attached patch.

I restrained from implementing that, I didn't want to change too many
key bindings.

Christoph
#224813#17
Date:
2006-07-23 15:32:07 UTC
From:
To:
The way I use the debfoster (clean up packages I've installed for
testing purposes), purging packages is the correct default.  Are there
any other use cases I'm not aware of where removing packages would be
preferable?

The point about misleading documentation is valid, though.
#224813#20
Date:
2006-07-23 15:32:07 UTC
From:
To:
The way I use the debfoster (clean up packages I've installed for
testing purposes), purging packages is the correct default.  Are there
any other use cases I'm not aware of where removing packages would be
preferable?

The point about misleading documentation is valid, though.