I've just started trying out R6 as I am getting questions about adapting my R5.5 How-to's for the Antec Fusion and Antec Veris.

I would rather work to ensure the correct libraries are included in R6 instead.

As I look at R6.0.0.8 I see that lirc is at version "0.8.5-CVS-pvr150". This doesn't seem to be an official snapshot so I can't quite tell what is in it. The only reference to it I can find is at http://www.blushingpenguin.com/mark/lmilk/ where the date on that file predates 0.8.5pre1.

Is that in fact what is currently in R6 (ie. an October '08 snapshot)?

Cecil, would it make sense to go to 0.8.5pre2 now?

incidentally, I have verified 0.8.5pre1 on two different installs with two different remotes/receivers on R5.5.

I cant speak for cesman, but I submitted a change to the R6 lirc yesterday in flyspray:
http://linhes.org/flyspray/index.php?do ... d&sort=asc

For the gory details of how I worked out how to build the package on R6, refer to:
http://knoppmyth.net/phpBB2/viewtopic.php?t=19849

If you can build a package that installs and works, that would be a great start.

Thanks for this. It also confirms my suspicion that the included lirc is actually a rather old CVS version of 0.8.5.

I'm not convinced that building the package in this way is the right way to do what I want for this distro. But admittedly I haven't built packages for Arch before.

My thought is that all of the changes I need in lirc are already in the official lirc.org cvs snapshots starting with 0.8.5pre1. So I think all that is required, is to include in the LinHES base at least pre1 (and pre2 would be better). I expect it is more stable than the earlier CVS builds.

From there, the additions I need to add are specific config files which I can tar-zip up for Cecil.

AFAIK everything is built as a package.
Things like the .lircrc and lircd.conf files must be from some other package. I'm trying to work out where they come from too.
If you need a newer version of lirc, the first step would be to modify the PKGBUILD for lirc so that it uses the newer version. There is a fair bit of work to do that and make sure it builds properly with all of the patches that are needed. The best way to progress that would be to do the work yourself and then submit a new source package for inclusion. To build a source package (like the one I attached to the ticket referred to earlier), you just run . It would be helpful if you started with the package that I submitted.

I think the lircrcs are in system-templates package.

hmmm. My understanding was that the official snapshots at lirc.org should have captured all of the patches to that point. So 0.8.5pre2 should have everything to the end of March.

Is this not correct?

I dont know. I think the reason that he uses the blushingpenguin sources is because that version has been patched to add some sort of support for the pvr150 (remote? or blaster?)? This is what makes upgrading more difficult. Upgrading and getting extra support for things that have been added to lirc CVS can mean that you might lose support for the 150 which was provided through the blushingpenguin sources.

In the past when I have made contributions to knoppmyth, I have also made sure that they get incorporated into the source pakage (I have done this for lirc and also dvb stuff). Im not sure if the same has happened for the blushingpenguin patches.