[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Removing former conffiles

On Tue, Feb 07, 2006 at 12:28:39AM -0800, Don Armstrong wrote:
> On Tue, 07 Feb 2006, Frank K?ster wrote:
> > Don Armstrong <don@debian.org> wrote:
> > > Just a word of caution here: If the administrator has modified the
> > > file, you should not rename or move it, as they may know better
> > > than you what they're doing. A proper course of action would be
> > > warning them, and/or offering to remove the files in question via
> > > debconf.
> > 
> > If I know that the file will no longer be read at all, there's no
> > point in pretending that it still have an effect. Renaming it makes
> > this completely clear. 
> Right. The problem is that it's not always easy to know if the file
> will no longer be read at all; you can't assume that the administrator
> has left in place your default configuration system. [Likewise for
> failure modes on the presence of an obsolete configuration file;
> unless you know for certain that it will fail, you should give the
> administrator some way to override your guess.]

The package is a dummy transition package.  When this version of gnocatan is
installed, no gnocatan config files will be read at all anymore.  It might
have been a good idea to try and convert it into a pioneers config file (the
new name of the package), but as long as the name includes "gnocatan", it's
not going to have any effect, since there are no binaries in the gnocatan-*
packages anymore (well, except this maintainer script).

Would that mean it's ok to remove it?  Or should I better rename it so they
can use it to convert to a pioneers file by hand?  Perhaps that's the best...
I could make a NEWS message about that as well.


I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
   in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see

Attachment: signature.asc
Description: Digital signature

Reply to: