From: Petri H. <Pet...@hu...> - 2006-12-25 05:30:38
|
On Mon, 2006-12-25 at 00:53 +0100, Reinhard Nissl wrote: > > How about creating self-compiling input plugin ? > > > > I mean, separating vdr and xine specific parts and having two packages, > > one as vdr server component (vdr-xine) and another as xine add-on input > > plugin (vdr://) ? It is quite easy to form a makefile for add-on xine > > input plugin. I belive such a separtation would make vdr-xine a lot > > easier for all distribution maintainers ... ? > > The idea is not bad but at the moment it doesn't work as my vdr-xine > related patch addresses for example libmpeg2. Once these parts of the > patch have been added to CVS, one could go on to either create > self-compiling vdr-plugins or to add them to xine too. > > One reason why there hasn't been any progress in this direction during > this year is that I was quite busy at work and at home with other > things. So, let's see how things evolve next year ... > I was just thinking it might be easier to push patches thru in smaller chunks. And, it is easier for package maintainers to make separate builds if there was separate input_vdr module. I agree your patch addresses several serious problems inside xine-lib, buy most parts of this "mega" patch could be implemented as simple separate patches unrelated to actual vdr-xine plugin (?). - Petri |