Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
We are (still...) trying to update the fedora lirc package. Partly, this
is about gettting the systemd setup correct.
One problem is the need to add the lirc protocol to
/sys/class/rc/rcX/protocols. My first attempt was to execute a 'echo
lirc > /sys/class/rc/rc0/protocols' before starting lircd. However,
this is not that simple:
- How can we know it's rc0 and not e. g., rc1?
- How do we know lircd is handling an ir device requiring this?. E. g.,
an RF remote shows up as an USB device and that should not add any lirc
Basically, it's seems hard to make this generic in a package. Another
solution might be to add an udev rule to all rc devices, but that seems
a little brutal (?)
Has lircd enough information to make this internally?
Any thoughts out there?