On 3 July 2012 07:51, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote:
VDR (and me, too ;-) doesn't care in what way a particular system boots
or starts its services.
It would be handy though, if VDR proper came default with a way to
toggle plugins on and off in the user interface.
Gerald Dachs wrote:
That's the current state. I can't think of a good reason why it has to
stay that way though. VDR itself could have a menu that allows to enable,
disable and configure plugins.
I can't see a benefit of this approach. At least for distributors it would get
more complicated to
On 02.07.2012, at 10:39, Manuel Reimer manuel.rei...@gmx.de wrote:
Gerald Dachs wrote:
That's the current state. I can't think of a good reason why it has to
stay that way though. VDR itself could have a menu that allows to enable,
disable and configure plugins.
I can't see a benefit of
On 3 July 2012 07:51, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote:
VDR (and me, too ;-) doesn't care in what way a particular system boots
or starts its services.
It would be handy though, if VDR proper came default with a way to
toggle plugins on and off in the user interface.
--
-Tor
Am 28.06.2012 09:01, schrieb Ludwig Nussel:
Manuel Reimer wrote:
Ludwig Nussel wrote:
Yes. Not only for better systemd integration but in general it would be
better if vdr could work without requiring any external scripting or
configuration.
You need some external script to call VDR as
Mika Laitio lam...@pilppa.org wrote:
On 06/28/2012 08:02 PM, VDR User wrote:
On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel ludwig.nus...@suse.de
wrote:
That would be a nice feature -- worth suggesting for the big `after
2.0 is released` redesign(?). But, there may be plugins which need
Manuel Reimer wrote:
Ludwig Nussel wrote:
Yes. Not only for better systemd integration but in general it would be
better if vdr could work without requiring any external scripting or
configuration.
You need some external script to call VDR as somewhere it is required
to configure plugins and
On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel ludwig.nus...@suse.de wrote:
You need some external script to call VDR as somewhere it is required
to configure plugins and plugin parameters and many more stuff, VDR
gets via command line options.
That's the current state. I can't think of a
On 06/28/2012 08:02 PM, VDR User wrote:
On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel ludwig.nus...@suse.de wrote:
That would be a nice feature -- worth suggesting for the big `after
2.0 is released` redesign(?). But, there may be plugins which need to
be initialized with certain values.
Paul Menzel wrote:
[...]
and the one shipped by openSUSE [2].
[Unit]
Descritpion=VDR
After=lirc.service
[Service]
Type=once
ExecStart=/usr/local/bin/runvdr
TimeoutSec=0
The reference to /usr/local makes it pretty obvious that
On 2012-06-27 12:48, Paul Menzel wrote:
looking around for systemd service files I found three examples.
The Fedora one and other related files are at
http://pkgs.fedoraproject.org/gitweb/?p=vdr.git;a=tree
___
vdr mailing list
vdr@linuxtv.org
Ludwig Nussel wrote:
Yes. Not only for better systemd integration but in general it would be
better if vdr could work without requiring any external scripting or
configuration.
You need some external script to call VDR as somewhere it is required to
configure plugins and plugin parameters and
12 matches
Mail list logo
