On Tue, 17 Jan 2017 03:12:49 +0530
=?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= <shirisha...@gmail.com> wrote:
> Adequate reported multiple obsolete-conffiles for lirc -
>
> [$] adequate lirc
>
> lirc: obsolete-conffile /etc/lirc/irexec.lircrc
> lirc: obsolete-conffile /etc/lirc/lircmd.conf
> lirc: obsolete-conffile /etc/lirc/hardware.conf
> lirc: obsolete-conffile /etc/lirc/lircd.conf
> lirc: obsolete-conffile /etc/lirc/lirc_options.conf
Hi!
hm... My strongest feeling about the debian configuration handling is
being on thin ice. That said, all of these files exists for reason.
The hardware.conf is indeed obsolete, and not really used from 0.9.4+.
But the upgrade from 0.9.0 to 0.9.4 is a breaking update requiring
manual intervention, mostly about moving values from hardware.conf to
lirc_options.conf. So it needs to around as reference for some cycles.
The other files are important configuration stuff. On what ground does
adequate deem them as "obsolete"?
Perhaps is the problem I havn't trusted the conffiles handlng of
configuration files but instead just created them in the maintainer
scripts? This is because lirc has been plagued by multiple upgrade bugs
based on this stuff, forcing user intervention. The policy here is that
we ship e. g. lirc_options.conf.dist which is upgraded but not actually
used. lirc_options.conf is created as a copy if lirc_options.dist if it
does not exist, but is otherwise left as-is. Does this upset adequate?
--alec
