Hi Marcel,
On Tue, 03 Sep 2013 22:59:40 +0200
Marcel Witte
I've created my own vdr repository for my own needs in the build service a few years ago (home:balta3:vdrdevel). I update this repository frequently and also created quite a few plugin packages (because I'm using THIS packages to watch TV everyday). But this packages are not going the "suse way", for example I'm not using sysconfig and an init script, but runvdr.extreme [1] and systemd. I also created my own rpm macros to get small and easy plugin spec files. (The Makefile of Plugins has changed in 2.0, so all plugins need to be touched anyway)
So I don't know if I would be the right maintainer, but I'm willing to help if possible ;)
Maybe I can be of assistance, at least for the "suse-fication" to start with. I maintain a local build in my private instance for own purposes, which takes your project as base, and is then patched to some extend to look like the old suse-supplied vdr. I "stole" some of the work from seife's vdr attemtps. I will move my vdr setup to my OBS:home and send you a PM, so you can have a look at it and perhaps I can submit it to your project for further use.
At least the some plugins are updated frequently, should VDR really be included in the main repository? Wouldn't a well maintained, official vdr repository be enough?
I myself maintain only very few plugins, basically remote and vnsiserver, only. The latter one is not OBS-able. Greetings, Stefan -- Stefan Botter Network Manager Jacobs University Bremen gGmbH Campus Ring 1 | 28759 Bremen | Germany Commercial registry: Amtsgericht Bremen, HRB 18117 President & Geschäftsführer: Prof. Dr. Heinz-Otto Peitgen Provost & Geschäftsführerin: Prof. Dr.-Ing. Katja Windt Chair Board of Governors: Prof. Dr. Karin Lochte