faad2 and faac

[Fabian Greffrath]

Am Montag, den 10.11.2014, 13:28 +0000 schrieb Julian Cable:
> Hi Fabian. The sourceforge upstream project have also already
> committed the changes and tagged them but don't know when/if they will
> do releases. So instead of the patch you could import an upstream vcs
> tarball. 

I have seen that with surprise! However, as long as our Debian package
does not fall back too far from upstream development (which is, ahem,
unexpected) I am reluctant to package an unreleased VCS snapshot.

> If we can agree on a release version number I can put it into the
> Debian dream package as a >= dependency and when you are ready we can
> package consistently. That will be a great help to anyone trying to
> run Dream on Debian and derivatives. 

The package revisions will be faad2 (2.7-9) and faac (1.28-7). I will
upload them as soon as my GPG key is added to the debian-maintainers
keyring or after the freeze -- whatever comes first. ;)

Regarding your dream package: Please add "Build-Depends: libfaad-dev (>=
2.7-9~)" to the debian/control file. If you make sure to link against
the correct library (i.e. the one with _drm in its name), the binary
package dependencies will be chosen appropriately.
Since faac is non-free, your package must not have a Depends or
Recommends relation with it. So, what remains is "Suggests: libfaac0".
Since weak dependencies, i.e. Recommends and Suggests, cannot be
versioned, you need another measure to make sure that the right libfaac0
package revision gets installed. Thus, please add an additional "Breaks:
libfaac0 (<< 1.28-7~)". This will upgrade already installed revisions of
this package, that do not contain the libfaac_drm library, and will also
prevent lower package revisions to get installed as long as the dream
package is installed.

Hope that helps.

Fabian


> Thanks for such quick work. 
> 
> Julian
> 
> > On 10 Nov 2014, at 10:38, Fabian Greffrath <fabian at greffrath.com>
> wrote:
> > 
> > Hey Julian,
> > 
> > I've just tested your approach with the faad2 package and it works
> just
> > as expected. I'll add the necessary changes to the Debian packaging
> soon
> > [tm]. But please note that we are not in a hurry: testing is
> currently
> > frozen and I see zero chance that faad2 will get a freeze exception
> with
> > a change as intrusive as this.
> > 
> > BTW, I have decided to put the renamed library into the regular
> libfaad2
> > package. It has a different name and weights only ~250kB. So, you
> only
> > need to take care to link your own application against the correct
> > library name. 
> > 
> > @team: Does anyone remember why we put the 10bit-libx264 into a
> > subdirectory instead of renaming the library? One has to use
> LD_PRELOAD
> > magic, anyway, to use it.
> > 
> > Thank you very much already!
> > 
> > - Fabian
> > 
> > 
> > cg==
> 
> _______________________________________________
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
>