next mplayer upload

Reinhard Tartler siretart at tauware.de
Tue Jun 9 10:28:41 UTC 2009


Fabian Greffrath <greffrath at leat.rub.de> writes:

> If we really happen to ship unmodified ffmpeg sources but disable some
> codecs in the binary package, what will the situation be in Ubuntu and
> Debian?

It won't change much. I already have "permission" to ship an unstripped
source in ubuntu/main.

> Will you still provide lib*-unstripped packages in Ubuntu with only
> the seven lines of codec-disabling commented out?

Yes, because the main benefit of doing is is the additional external
libraries I can depend on in the unstripped branch. The most important
ones include x264 and libmp3lame. the name "unstripped" is clearly
misleading, so at some point we should clear up the naming. However I
don't think this is a good time to implement such a change, at least not
until we don't know how debian stands here.

> And how about Debian? Will we still try to get the package into the
> non-free section without the codec-disabling or do we leave this as an
> exercise to the user? ;)

TBH, I'm still in favor of shipping an build-and-install shell script in
/usr/share/doc/ffmpeg that downloads and builds from git all packages
that we are not able to provide in debian proper.

BTW, in order to get there, I think the packages mp3lame and x264 should
be updated so that the master.unstripped branch can be built against
them. IIRC both packages haven't been moved from svn to git yet, so I'll
work on that next. Since ubuntu does ship these packages, I'd like to
maintain them under the pkg-multimedia umbrella. Any objections?



-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4



More information about the pkg-multimedia-maintainers mailing list