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

Re: [copy, not move of conffile] How to warn about need to port changes to new configuration file?

On 18/06/2010 16:57, Petter Reinholdtsen wrote:
> [Thomas Hood]
>> It is planned that an upcoming version of resolvconf will add a new
>> hook script for isc-dhcp-client which is identical to the existing one
>> for dhcp3-client.  An administrator who has made local changes to the
>> latter hook script should probably make the same changes to the
>> former.
>> Is there a need to warn the administrator that he should (presumably)
>> re-implement his changes in the new file?  If so, what is the best way
>> to warn him?  Should debconf notes be used?
> What about moving the file in the preinst, and/or create a symlink
> to/from the new location instead?  I mean like renaming conffiles is
> normally handled.  This way any local changes are kept, and the new
> location work without any manual intervention.

The difference here is that this is a copy, not a move, of the conffile.
The old one in resolvconf is still needed if the admin still uses
dhcp3-client. The new one (a copy of the previous one) is required for
  The problem is how to handle local modification of the first conffile.
I see several possibility:
[A] unconditional warning in NEWS.Debian
[B] conditional warning (if the first conffile has been modified) with
  a debconf note
[C] copy in postinst of the first conffile to the new one, overriding
  the one provided in the package, if there has been modification in the
  first conffile.

Of courses, A, B and C can be done in any combination. A+B+C can be a
good solution...


> Happy hacking,

Vincent Danjean       GPG key ID 0x9D025E87         vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A  8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://perso.debian.org/~vdanjean/debian unstable main

Reply to: