Package Base Details: vdr

Git Clone URL: https://aur.archlinux.org/vdr.git (read-only, click to copy)
Submitter: lotho
Maintainer: CReimer (M-Reimer)
Last Packager: M-Reimer
Votes: 63
Popularity: 0.001738
First Submitted: 2006-06-19 17:17 (UTC)
Last Updated: 2024-04-24 18:09 (UTC)

Latest Comments

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

M-Reimer commented on 2019-01-18 20:37 (UTC)

No, no additional patches. Sorry for that, but additional patches just make it more difficult to update in future.

If you need dynamic device detection for whatever reason, then please contact the VDR developer directly to place your feature request.

marlemion commented on 2019-01-18 11:07 (UTC)

Would it be possible to include the dynamite patch?

http://www.schuld.org/vdr-2.4.0-dynamite.diff

This would enable the building and usage of the dynamite plugin. Patch applies and builds.

ILMostro7 commented on 2017-12-27 11:11 (UTC) (edited on 2017-12-27 11:17 (UTC) by ILMostro7)

Still fails to build for me. Latest update submitted 20170908 would suggest project is not abandoned/orphaned. However, latest patch works: https://ip6.li/node/127

83fd4c18bea05588 commented on 2017-12-07 11:22 (UTC)

Patch which fixes problem reported by jtts:

https://ip6.li/node/127

jtts commented on 2017-06-22 18:50 (UTC)

Build fails with GCC7. A patch to fix this is available in the VDR mailing list: https://www.linuxtv.org/pipermail/vdr/2017-March/029229.html

CReimer commented on 2015-04-14 11:01 (UTC)

I don't know of any drawbacks with the ttxtsubs patch. But nevertheless. It's not right do add more patches downstream. If you want ttxtsubs you should talk to the upstream maintainer. In one of the next updates I'll remove the MainMenuHooks patch, too.

jpalko commented on 2015-04-13 18:56 (UTC)

Have you happened to have tried out whether the newer ttxtsubs patches cause issues anymore? Was just checking that there are now vdr-2.0.6-ttxtsubs.patch and vdr-2.2.0-ttxtsubs.patch versions of it.

azleifel commented on 2015-02-19 22:06 (UTC)

Due to other commitments, the update to 2.2.0 will follow in the next few days.