Package Base Details: vdr

Git Clone URL: (read-only, click to copy)
Submitter: lotho
Maintainer: CReimer (M-Reimer)
Last Packager: M-Reimer
Votes: 61
Popularity: 0.000978
First Submitted: 2006-06-19 17:17
Last Updated: 2021-01-07 15:34

Packages (2)

Latest Comments

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

eworm commented on 2014-01-20 08:32

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/.


azleifel commented on 2014-01-19 22:45

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

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:


The dash should make the script execute only if it exists.

azleifel commented on 2014-01-09 19:45

* Updated to version 2.0.5

azleifel commented on 2013-10-25 21:06

* Updated to version 2.0.4

azleifel commented on 2013-09-01 15:38

* Updated to version 2.0.3

azleifel commented on 2013-08-12 19:06

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.

azleifel commented on 2013-08-11 20:24

PS. linux-api-headers 3.8.4-1
Kernel headers _sanitized for use in userspace_

The headers version doesn't have to match the kernel version

azleifel commented on 2013-08-11 20:22

Just rebuilt vdr locally and it still works fine with my dvb-t cards. The issue probably isn't with the

vdr[28034]: DVB API version is 0x050A (VDR was built with 0x0509)

message. How are you starting vdr? If you're not using any plugins, what are you using for video output?

azleifel commented on 2013-06-08 17:15

No connection. ArchVDR is a comprehensive solution with all the bells and whistles and the packages I maintain give a simple but still functional installation.