Support open standards! Aim for XHTML 1.0 Strict compliance!
There has been several changes from lirccd 0.8 to 0.9. If you are upgrading from any 0.8 version of lirccd, neither lirccd nor any programs written to use it will work. Read this for info on how to make them work. If you have any questions that are not answered here, please mail them to me (the address is at the bottom of the page).
No disturbing changes have been made to the file format itself, although that, too, is planned for a near future. These will be relatively minor, though.
However, lirccd no longer uses the filename ~/.lirccrc, but ~/.lircrc. Just rename your configuration file and you should be fine, or use the -C option to specify ~/.lirccrc explicitly.
This is where the major changes have taken place. liblircc has been obsoleted and no longer works. I recommend that you remove liblircc completely from your system if you intend to use lirccd 0.9. Instead, lirccd 0.9 ships with a modified version of the standard liblirc_client. This means that programs that already have liblirc_client support will support lirccd "out-of-the-box", so to speak. The new liblirc_client contains new functions that are lirccd-specific, but retains binary compatibility with programs using the old liblirc_client API. If a program that uses liblirc_client is started and lirccd is not running, liblirc_client will start lirccd with the -c option. The -c option makes lirccd terminate when the last client disconnects from the socket. For information on the new calls and how to make your programs work with the new liblirc_client, see the README.
The protocol has also been completely revised. If you have designed a program that uses the protocol directly, I recommend that you rewrite the lirccd interaction part to use liblirc_client instead, since the new protocol is more complex (and also since I haven't documented it ;-) ). This also means that the old patches for MPlayer won't work, since they use the protocol directly. However, with the new liblirc_client, you won't need to patch MPlayer, or any other programs, at all.
Support open standards! Aim for XHTML 1.0 Strict compliance!