Le 11.10.2013 00:49, Gregory Nowak a écrit :
On Thu, Oct 10, 2013 at 11:23:50PM +0200,
berenger.mo...@neutralite.org wrote:
Maybe you, since you know how it works. But, someone with no
knowledge would think that it also removes userland configuration
files, since it claims to remove all configuration files.
Ok, since the man page is saying one thing, and yourself and Brad are
saying another, I decided to try this out. Here's what I did:
[snip]
Yes, I know that this is the normal behavior. It purged system-wide
configuration. But, the point is, that for some people, when they read
the man page, they think that it removes *all* configuration files,
including the ones the application have created in userspace. Which it
does not, we all agree about that.
Now, the question I asked was, should the manpage be fixed to avoid any
user to think that dpkg can remove all configuration files, including
those which were not created by dpkg, since some applications create
some config files themselves ( so, the user does not create them not
manipulate them without that application's dedicated interface ) which
can makes things confusing.
But, yes, definitely, people with knowledge about dpkg, even as small
as mine, understand that it does only remove files it have created.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/d3b78415d892ee8b8888e81511c46...@neutralite.org
