Bug#405224: ITP: vdr-plugin-epgsearch -- VDR Plugin that provides an extended schedules menu

[Christian Meder]

On Wed, 2007-01-03 at 23:50 +0100, Thomas Schmidt wrote: 
> * Christian Meder schrieb am 03.01.07, um 21:27 Uhr:
> > Let me know where I should start.
> 
> First you should take a look at [1] and maybe the documentation of 
> svn-buildpackage and setup a local working copy of the packages you
> are interested in. (plus the tarballs directory as we are using the
> mergewithupstream-mode of svn-buildpackage and we keep all the
> upstream tarballs in the tarballs directory)

Ok. Will do.

> > Actually I checked the pkg-vdr-dvb project and wnpp before posting my
> > ITP. At least to me the link to the subversion repo wasn't obvious. I
> > checked the cvs repo which is linked from the project page and noticed
> > that the mail archive holds mostly spam. So I went ahead and ITPed.
> 
> Yes, thank you for pointing this out, if now deactivated the
> SCM-Component on the alioth-project, as i did not find a way to let it
> point to the svn-repository instead of the old cvs one. ;-)

I just noticed it. Thanks. 

> > BTW what's holding the unreleased packages from entering the main Debian
> > archive ? Lack of manpower or some other specific plan ? Could we at
> > least ITP the external packages which are expected to enter the archive
> > in the short term ? this would potentially help confused people like
> > me ;-)
> 
> Well, as Tobias said allready, the plan was to add a few plugins to
> the archive after the release of etch, but i guess another reason for
> the missing ITP's is just a lack of time. (Most packages in the
> svn-repository are in a releasable shape, but in a few cases there are
> legal questions, especially with some packages in Tobias's private 
> repository.)

Is there a list of the packages with possible legal issues somewhere ? 

> Another reason for being rather conservative with uploading too many 
> new plugins may be that upstream is quite dead on a lot of plugins
> and i do not really want to become the new upstream for these packages. 
> (vdr-plugin-weather is a good example, it is allready in the archive, 
> but upstream is dead and we spent quite some time to port the plugin 
> from vdr 1.2.x to 1.4.x.) ;-)

But IMHO that's not a big problem per se. If a plugin can't be easily
ported to a future release there's always the option of just dropping it
from the distribution. 

I maintain the flying package since almost 10 years and it still only
works on a 8bit display depth (which is rarely used these days) because
nobody spent the effort to patch it to work on other display depths.
Nevertheless it hurts nobody and can be easily dropped if need be. 

Ok, packages which are expected to explode easily and in creative ways
and which are abandoned upstream should get blocked from getting into
testing. But unstable should be ok. Experimental if you want to be
careful. 

I'll shut up now and start on the packages which I mentioned in the other mail.

Greetings,


				Christian

-- 
Christian Meder, email: chris at absolutegiganten.org

The Way-Seeking Mind of a tenzo is actualized 
by rolling up your sleeves.

                (Eihei Dogen Zenji)