beta2 ongoing development

[mk01]

(14th Aug, 2013 03:06 AM)f1vefour Wrote:  That would work but I think my way is more ideal because a user can create his own configuration in /home without the messiness of adding a big remote configuration to a system level file (/etc/lirc/lircd.conf).

The way I described is more proper and if course I tested it and verified it works by adding the include.

Also most people don't know if they should allow the package maintainers version to overwrite their version, this causes confusion.

I personally prefer my way but since your the developer you should choose.

you can stay with you config, it doesn't matter.
whole /etc is there for modification by user. it is purpose of it. config files should never be overwritten by maintainer and this is clearly stated. there are deb helper tools to help maintainer with updating conf structure to a new version while keeping users configuration. packages which does not follow this rule are never put into distribution. if really high demand, then they go to extra section of repo, but never main.

simply that's the wrong way.

lirc was even hiding scripts under .conf files, stored under /etc …

your approach is commonly used for multiuser systems (ssh key storage, bash rc / profile etc) …

if you have 20 minutes, please upgrade lirc to 1.4-7. conf files should be kept, just for sure do a copy of /etc/lirc before.