First ebuild. I probably misinterpreted the docs or missed a step or two but here goes... irTrans is a hardware infra-red receiver that's common to quite a few different integrated pieces. The developers of the irTrans hardware have an open source server software which replaces* lircd but is 'compatible' with LIRC clients. Developers of the software seem to still be actively working on it and adding support for more devices so it makes sense to make an ebuild for it. *lircd can be run alongside irserver if the proper irserver cl args are given. Reproducible: Always Steps to Reproduce:
Created attachment 110520 [details] basic ebuild for irserver
Created attachment 110521 [details] irserver-24-01-07.ebuild (r1) changed a cp in the final statement to dosbin ... not sure if I'm supposed to declare 'into /' first or if we can leave that assumed.
Created attachment 112594 [details] remotes.tar.gz I've been away from this for a bit and I seen no one has picked it up as a maintainer yet but I just wanted to note a couple things I've noticed as I've begun to work on it. The first is that there are two binary outputs to this, irserver and irclient. irserver is the lirc replacement server but irclient is a remote trainer for remotes that haven't yet been configured. Currently irclient fails compilation and I'm not a c programmer but I have a buddy who is who's looking at it and might get a patch prepared. Also, I've found (after some exhaustive guessing) that the irserver and irclient binaries are looked for in '/usr/share/irserver/bin'. This default location for the binaries seems sloppy and against lfs convention so I have intention of issuing a patch (again when time allots) to change any references to irserver and irclient to /usr/sbin and /usr/bin respectively. Lastly, attached is a folder called 'remotes' with several preconfigured plaintext remote profiles. These are not currently available in linux upstream but were found in the windows variant upstream and are compatible. Upstream has been contacted but it is unknown whether or not they will include these. If this package makes it into the tree I recommend hosting these profiles with the tree as part of the package. Target is /usr/share/irserver/remotes ~Chad
Created attachment 126429 [details] app-misc/irtrans-irserver-5.8.18-r1.ebuild This is an different Ebuild for the Irtans Server it also has an initscript and compiles fine on amd64 system. plz reasign this bug to vdr@gentoo.org
Created attachment 126431 [details] files/irtrans-server.confd This is the needed conf.d file
Created attachment 126432 [details] files/irtrans-server.initd The init.d file
Assigned to vdr@g.o
Created attachment 127689 [details] app-misc/irtrans-irserver-5.9.01.ebuild Update to the latest release. Now with real amd64 support with full ccf support (analog recording if the irsignal).
Created attachment 128257 [details, diff] irtrans-irserver-5.9.01-missing-include.diff atached diff fix compile errors, depend on missing include. Mario or Chad, if somebody contakt upstream, this should be fixed in next Version. @ Mario can you upload the remote.tar.gz to your webspace ( add a versions Nr. eg remote-0.0.1.tar.gz ) and tell me plz the URL.
Comment on attachment 126431 [details] files/irtrans-server.confd ><?xml version="1.0"?><html><body><pre># Controls which information is logged. Standard is loglevel 1. # Config for irtrans-server # $Header: $ ># Possible values are 0-4. 0=Nothing is logged. 4=debug output. >LOGLEVEL="1" > ># Starts the irserver as a LINUX Service. >OPT="-daemon" > ># LINUX Devices: /dev/ttyS0 - /dev/ttySn or /dev/ttyUSB0 - /dev/ttyUSBn for USB devices >IRDEVICE="/dev/ttyUSB0" ></pre></body></html>
Created attachment 128269 [details] fixed init file
(In reply to comment #9) > Created an attachment (id=128257) [edit] > irtrans-irserver-5.9.01-missing-include.diff > > atached diff fix compile errors, depend on missing include. > > Mario or Chad, if somebody contakt upstream, this should be fixed in next > Version. > > @ Mario > can you upload the remote.tar.gz to your webspace ( add a versions Nr. eg > remote-0.0.1.tar.gz ) and tell me plz the URL. > i have already contacted upstream (waiting for response) in the binary release there are also the remotes included so we will not have to maintain something like remotes package i will upload the binary with a version number and will ask if upstream can include the remotes in the next source package. the source for all renamed packages is ftp://mars.arge.at/irtrans/ or http://ftp.mars.arge.at/irtrans/ wfg Mario
Created attachment 128281 [details] app-misc/irtrans-irserver-5.9.01-r1.ebuild updated ebuild that includes the remote samples.
Created attachment 128285 [details] app-misc/irtrans-irserver/files/irtrans-server.initd this is the corrected init file from hd_brummy servers should go to /usr/sbin this is the corrected init script wfg Mario
Added to Portage, iam let irserver install to /usr/bin ;) Thanks for the good work, Mario, again: How did we talk before on vdr-portal.de, iam added you as proxied maintainer. MfG Joerg
(In reply to comment #15) > Added to Portage, > > iam let irserver install to /usr/bin ;) > > Thanks for the good work, > > Mario, again: > > How did we talk before on vdr-portal.de, iam added you as proxied maintainer. > > MfG > > Joerg > how i will inform you for new releases ? reopen the bug or create a new one or mail you directly ? should the irserver not go to sbin ? wfg Mario
(In reply to comment #16) > > > how i will inform you for new releases ? > open a new bug for this, bugwrangler will assigne the bug directly to maintainer listed in metadata.xml > should the irserver not go to sbin ? Iam not shure, usr = user. Software für die Nutzer. bin = binary. Das Verzeichnis enthält Binär-Dateien, in der Regel aufrufbare Programme. sbin = system binary. Verzeichnis mit Programmen für den System-Administrator. (sorry for german) a point for trouble ;) /usr/bin or /usr/sbin both should be ok
