the unstripped ffmpeg source package

Reinhard Tartler siretart at tauware.de
Sat Oct 4 14:36:02 UTC 2008


I finally got around to actually create the 'unstripped' ffmpeg source
packages. you can find the sources here:

https://edge.launchpad.net/~motumedia/+archive

The source is managed in bzr here:

https://code.edge.launchpad.net/~motumedia/ffmpeg/ubuntu.unstripped

I decided to to this in bzr instead of svn because merging changes is
way more easier for me than with svn. Early adopters of those packages
confirm that the libavcodec-unstripped-51 package actually works for
them and enables them to use ffmpeg as expected.

Now, how do we want to proceed from here? We could of course produce
unstripped libavcodec packages for debian as well, but where to host it?
TBH, I don't see much problem in hosting them on alioth.

Next, how to manage the source package? Having both packages seperatly
is just unmanagable, even with bzr it is still a bit a PITA, with svn I
even refuse to try it. I therefore suggest the following:

 - make the debian/rules file check what package we are talking about in
   debian/changelog. Depending if the last changelog entry mentions as
   source package 'ffmpeg-debian' or just 'ffmpeg', copy and concatenate
   appropriate fragments of debian/control. See next.

 - debian/control is generated via debian/rules:

    - debian/control.source: contains the stanza for the source
      package. The first line ('Source:' field) needs to be generated
      according to what is in debian/changelog, see above.

    - debian/control.ffmpeg-debian: contains the rest of what we
      currently have in debian/control

    - debian/control.unstripped: contains just the unstripped variants
      of the library packages.

 - drop the switch in DEB_BUILD_OPTIONS. We currently check that
   variable to see if we need to 'fixup' the config.h with the encoders
   we stripped. This can be done depending on the contents of
   debian/changelog.

With this I think we can manage the -unstripped- replacement packages
more easily. I see the current packaging of the replacement packages as
'proof-of-concept' solution, and would like to integrate them in the
regular source package.

Feedback on this appreciated!

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



More information about the pkg-multimedia-maintainers mailing list