Re: init script config files
Ethan Benson wrote:
> the only dubious argument i have seen is that when you change that
> single variable dpkg will need to ask you what to do about the script
> if the maintainer updates it (which IME is quite rare)
My experience is it happens fairly frequently (I maintain 8 init scripts on
my home system to which I have made changes.)
> the more i think about it the more i think even a config.d is not
> really a good idea. it really does not solve the upgraded script
> question since the script may change in such a way that obsoletes or
> changes the config.d file.
The config.d system makes the files sufficiently simple to parse that packages
can deal with fixing them up after such changes.
--
see shy jo
Reply to: