Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Wishlist for next vdr-Versions / Debian packaging



Hi!

First of all: Congratulations to all who worked hard to make this cool
piece of software happen. Especically to Klaus.

Maybe it's a little imsolent to start a wishlist for next version, but I
have had some ideas but no time to write them down.

From a vdr-users sight: It would be cool if vdr checks for available
plugins in a plugin-directory and present all found plugins on an
OSD-Page where one can enable the desired ones.

This might introduce plugin dependencies and conflicts. 
ie a plugin x can claim to depend on another one and can only be enabled
if the other is available or enabled.
Vice versa a plugin can claim to conflict with another on and can only
be enabled if the other is disabled.

ATM I haven't looked deep into the code, but it would be nice if the
plugin is not loaded on vdr startup but when it's needed. Ie. if I
select DVD on Mainscreen the dvdplugin will be loaded and unloaded if I
leave the DVD-Playback. (like the kernel-module-loader)


From a application packagers sight:
(First: I use Debian GNU/Linux and the Debian VDR package is nearly
unmaintained and needs a lot of work. The current maintainer no longer
owns a dvb-card which makes development difficult In about two month
I have some spare time and planned to bring this package in a better
shape.)
I already did some work, and ran into some problems with the new plugin
system. 
It would be nice if the plugins would build without being unpacked in
the vdr-source-tree.
Until now I managed to build recent vdr-packages (1.1.32)
 - 4 different binary-packages (Debian Maintainer decided to have these
   for different controls: kbd, lirc, rcu, none[daemon])
 - 1 package containing man-pages, documentation...
 - 1 development-package containing all include-files.

The idea is to have plugin-packages seperated from vdr-packages.
Advantages:
  - The user can install only desired plugins.
  - New plugin versions can be build and distributed without building
    vdr packages.
  - Plugins can be built without having vdr but the vdr-dev package
    installed

This requires to have a development-package (vdr-dev).

ATM the vdr-packages build with no problem, and I can build a seperate
dvd-plugin package which works, but I have to change a lot things in the
makefiles.
I tried to build a vcd-plugin package. The package build, but vdr
segfaults when loading this package. I had no time to find out why.

Maybe there are some Makefile/autoconf/automake/configure/whatever :-)
experts which could help to build a framework for building vdr with this
means and also create a framework for plugins.



For Debian-Users:
You can find my work (based on Eduard Bloch's offical vdr and dvb
packages) at http://hitchhiker.rz.uni-konstanz.de/video

Beware these packages are a messy hack but they work (at least for me
:-)).

They have neither right dependencies nor proper documentation.
Work slowly in progress :-)
Any help always welcome.

-- 
Heute ist nicht alle Tage, ich komm' wieder, keine Frage!!!

   Joerg

Good news from afar can bring you a welcome visitor.

Attachment: pgp00001.pgp
Description: PGP signature


Home | Main Index | Thread Index