What about turning the package of Lirc (the remote control program) inside-out and package the source code and the necessary devel files to the user?
Then create a nifty icon in the menu for the setup. This leads to devel files and compiler to the user install, but IMO heavily outweighs the trouble with configuring LIRC (and not to speak of the DMKS issues) that is very fine-tuned and well-functional in the LIRC setup.sh (that is removed in the current rpm).
This gives an abstraction layer to the program, so we just need to update it regularly and leave the details to the Lirc dev's.
I didn't know I needed the i2c kernel module in my setup - the setup.sh just told me this...i've spent hours getting LIRC to work properly and a new rebuild of Lirc still is troubled with missing devices and kernel modules.
When the user need LIRC, then he/she run the setup.sh (from the menu) and configure the hardware for the remote - then the configure script is run, program built and installed. Wrapper scripts can "make uninstall" and "make clean" where necessary (there is even a possibility the LIRC setup handles this).
The BEST way of running this (also in my opinion) would be to package it as usual, and then let the user be able to run the LIRC setup.sh script without compiling. Not sure this can be done without the lirc dev's.
any opinions - should I give it a go?