vdradmin depends on vdr. Is it possible to have the ebuild be "standalone" i.e. have vdradmin use an vdr on another machine ? (I have vdr running on a VERY small machine which could not handle vdradmin..) Yours, Nils Reproducible: Always
How should this work? vdradmin-am read some local files of VDR, i.e /etc/vdr/setup.conf /var/vdr/epg.data /etc/vdr/channels.conf ...
(In reply to comment #1) > How should this work? > > vdradmin-am read some local files of VDR, > i.e /etc/vdr/setup.conf /var/vdr/epg.data /etc/vdr/channels.conf ... > It does read setup.conf and channels.conf ? At least the sources I have on my system doesn't do that. And epg.data access is configurable. From my pov this should work, if we change "need vdr" in init-script to "use vdr".
(In reply to comment #1) > How should this work? True, "vdradmind.pl --config" asks for server-name and two Paths (config + video), which need to be accessable. Shouldn't be the Problem to ask the user to configure vdradmin, right ? IMHO The "problem" would be to add an "vdr" use-flag (or "no-vdr"), which determins if the ebuild (including config and start-script) should behave just the way it is today or if vdr is not needed (and the user is required to run "vdradmind.pl --config" or edit the config-files accordingly)
(In reply to comment #1) > How should this work? > > vdradmin-am read some local files of VDR, > i.e /etc/vdr/setup.conf /var/vdr/epg.data /etc/vdr/channels.conf ... I'm the VDRAdmin-AM maintainer and I can confirm that VDRAdmin-AM also works if VDR is running on another machine. There are three "drawbacks": 1) It reads some VDR configuration files (reccmds.conf and commands.conf). If they are not found the user won't see those commands in the Web UI. 2) It needs the video folder to export a recording's playlist (aka recording streaming). 3) It looks in tthe video folder's epgimages folder for EPG images imported by for example tvmovie2vdr. Regards, Andreas
(In reply to comment #2) > > From my pov this should work, if we change "need vdr" in init-script to "use > vdr". > I successfully use vdradmin-am without vdr on a remote machine now. I have just removed the vdr dependency and set "use vdr" instead of "need vdr" in the init script. For the drawbacks mentioned. If somebody wants to control the vdr from remote it has less sense to install the vdr on the remote machine, just because it needs some files from vdr. The files installed on the remote machine which vdradmin-am is reading are useless anyway as the interesting files are on the vdr machine. So what about adding a local "no-vdr" " use flag and if it is set change the init script accordingly.
Created attachment 149121 [details, diff] patch for using vdradmin-am standalone I have changed the ebuild and added a vdr USE-flag which pulls in media-video/vdr if set. It also installs a different init-script if USE=vdr is set with "depend() {need vdr}" and if unset with "depend() {use vdr}" Maybe using EAPI=1 is a good idea so "+vdr" could be set to make it a default USE-flag. Plus maybe adding some elog info which refers to this bug and comment #4, so that everybody is aware of the drawbacks by using this configuration. Regards, Daniel
I second that, although I would even call it a bug in its current state rather than an enhancement. As mentioned by the VDRAdmin-AM maintainer there is no real dependency to have vdr on the *same* box, and even the mentioned drawbacks are not necessarily true: I.e. I'm running a diskless vdr with nfs-root. The nfs server is running vdradmin, so it *has* access to vdr's config files... Best regards, Christian
Created attachment 159555 [details, diff] patch for using vdradmin-am standalone updated the patch for vdradmin-3.6.2
Created attachment 159556 [details, diff] changed init script
Created attachment 159557 [details, diff] new init script for needed with USE="vdr"
vdradmin-am-3.6.4-r1 includes now the use-flag vdr, enabled by default on EAPI=1 handling I have changed generally depend() handling to "use" in the initscipt, its in all cases enough to start vdradmin-am added also some info to force the user to give access to vdr's epg.data Thanks to all Contributors
(In reply to comment #11) > vdradmin-am-3.6.4-r1 includes now the use-flag vdr, > enabled by default on EAPI=1 handling There is no -r1 ebuild in the tree! hd_brummy did you forget it or did something went wrong with cvs? Regards, Daniel
Created attachment 178377 [details, diff] vdradmin-am-3.6.4.diff I have created an ebuild according to the changes you mentioned above.
Created attachment 178379 [details, diff] vdradmin-4.diff Changed dependencies from need vdr to use vdr
Sry, iam a little bit worry, forgot to commit, its in the tree now Thx billy, to point me
