AUR (en) - vdr

Search Criteria

Package Details: vdr-examples 2.7.3-1

Git Clone URL:	https://aur.archlinux.org/vdr.git (read-only, click to copy)
Package Base:	vdr
Description:	Plugins for vdr to show some possible features
Upstream URL:	http://tvdr.de/
Licenses:	GPL-2.0-or-later
Submitter:	lotho
Maintainer:	CReimer (M-Reimer)
Last Packager:	M-Reimer
Votes:	63
Popularity:	0.000014
First Submitted:	2006-06-19 17:17 (UTC)
Last Updated:	2024-12-17 18:20 (UTC)

Git Clone URL:

https://aur.archlinux.org/vdr.git (read-only, click to copy)

Package Base:

vdr

Description:

Plugins for vdr to show some possible features

Upstream URL:

http://tvdr.de/

Licenses:

GPL-2.0-or-later

Submitter:

lotho

Maintainer:

CReimer (M-Reimer)

Last Packager:

M-Reimer

Votes:

Popularity:

0.000014

First Submitted:

2006-06-19 17:17 (UTC)

Last Updated:

2024-12-17 18:20 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »

azleifel commented on 2014-01-20 20:44 (UTC)

I have several objections: 1. Scripts really shouldn't be run from either /var/lib or /etc. 2. vdr normally needs to be invoked with multiple command line parameters. This is what I'm using currently: /usr/bin/vdr --cachedir=/var/cache/vdr -c /var/lib/vdr -E /srv/vdr/video -l 2 -L /usr/lib/vdr --lirc --localedir /usr/share/locale --no-kbd -P epgsearch -P extrecmenu -P femon -P streamdev-server -P suspendoutput --menu --logo -P trayopenng -c eject -d /dev/dvd -P xineliboutput --local=none --remote=37890 --resdir=/usr/share/vdr -u vdr -v /srv/vdr/video -w 90 3. My runvdr-extreme package already does what you appear to want.

eworm commented on 2014-01-20 08:32 (UTC)

Project managers do have stupid ideas about how to install software... There is no need to follow these stupid advises when it works a lot better otherwise. With "non-standard" you refer to what the project manager states in the INSTALL file? How about the Filesystem Hierarchy Standard (FHS) [o] every software (and distribution) should follow? Place the scripts in /etc/vdr/ if you prefer that. But no one except pacman should ever create and/or change files in /usr/. [0] http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

azleifel commented on 2014-01-19 22:45 (UTC)

Thank you for your suggestion eworm. My package provides a standard, per INSTALL file, installation of vdr and the service file I've included supports a standard installation. Your systemd unit is most definitely non-standard, in addition to proposing that executable files be placed in /var/lib.

eworm commented on 2014-01-15 09:24 (UTC)

Generally forcing the admin to write files to /usr/bin/ is a bad idea, expecting any kind of configuration there is even worse. If this kind of stuff is really needed... How about changing the systemd unit to contain something like this: ExecStartPre=-/var/lib/vdr/init.sh ExecStart=/usr/bin/vdr ExecStopPost=-/var/lib/vdr/uninit.sh The dash should make the script execute only if it exists.

azleifel commented on 2014-01-09 19:45 (UTC)

* Updated to version 2.0.5

azleifel commented on 2013-10-25 21:06 (UTC)

* Updated to version 2.0.4

azleifel commented on 2013-09-01 15:38 (UTC)

* Updated to version 2.0.3

azleifel commented on 2013-08-12 19:06 (UTC)

My experience is that VDR doesn't segfault if the vdrsymbols font isn't installed, which is why it's an optional dependency. The extrecmenu plugin does, however, depend on the vdrsymbols font. I've fixed the install file. The install script is still bad because it assumes that the vdr user is to be called "vdr". If there is a preexisting user called vdr, created for some other purpose, then that user will find that they own all of vdr's settings files. I've always found the MANUAL that comes with vdr (installed in /usr/share/doc/vdr) to be usefully informative.