lircd.conf is where people using LIRC (Linux Infrared Remote Control) store their SPECIFIC remote control settings/codes. It is a file that etc-update should leave alone and stop complaining about. If a user lets etc-update "update" the lircd.conf, they will immediately lose all LIRC functionality upon LIRC restart or system reboot. They will then have to go retrieve their remote codes again if there is a pre-existing lircd.conf on the net, or otherwise go through the painstaking process of doing a button-by-button configuration of the entire remote. Reproducible: Always Steps to Reproduce: 1. emerge lirc 2. etc-update 3. Actual Results: If user doesn't overwrite, etc-update will keep nagging. If user does overwrite, lircd is toast upon system reboot or lirc restart. Expected Results: Leave lircd.conf alone -- many users -- especially MythTV users -- will have no reason to change this file when it's set. Even though this is "kinda" picky, I made this bug critical because it results in data loss in lircd.conf -- something I assure you one doesn't want to have happen if they have programmed lirc for an unusual remote from scratch.
lanius, you could try a solution like this: pkg_preinst() { cp ${ROOT}/etc/lircd.conf ${IMAGE}/etc } And that will cause lirc to just merge the same file into the filesystem that was in the filesystem before. The advantage is that even if you make a binary package, preinst happens premerge on that as well, so it's always the current file that gets merged onto itself.
ok, done
