Re: NEVER remove log files without asking
On Wed, Aug 18, 2004 at 05:48:02PM -0400, Glenn Maynard wrote:
> Yes, everyone here knows that. The point is that these, along with
> other semi-configuration-files, are left behind on --remove; saying
> "if you want logfiles left behind, use --remove instead of --purge"
> is ignoring the fact that plenty of other stuff is left behind, too.
But if it that was a bug that needed fixing, we'd need a third level of
--remove --keep-data or similar - and transient package states - even
less tested, even more inconsistently implemented.
Currently a package is inactive after removal (but configured, possibly
leaving some garbage around); and gone after a purge as if it had never
been installed. Granted, it's more important that it never removes a
file that it doesn't own. However, it should remove all that it can
from its default configuration and yes, in some cases parsing its own
configuration files might be the best way to get the rest.
Nick.
--
Nick Bannon | "I made this letter longer than usual because
nick-sig@rcpt.to | I lack the time to make it shorter." - Pascal
Reply to: