[Pkg-icecast-devel] backporting icecast and ezstream
dr at jones.dk
Fri Jul 18 17:10:49 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Jul 18, 2008 at 05:10:36PM +0200, Romain Beauxis wrote:
>Le Friday 18 July 2008 16:55:43 Jonas Smedegaard, vous avez écrit :
>> >You can link against library from bpo, but you need to be very carefull
>> > with the versions, since the build-dep resolver is, ahem..., complicated,
>> > and cannot be simulated beforehand...
>> ...which means you don't really know what you've got: Imagine
>> backporting ffmpeg, backporting some packages against that ffmpeg, and
>> then update the ffmpeg backport. Is "binNMUs" then done automagically?
>No. binNMU for bpo would be a killer feature for sure.
>> Yes, the problem is similar to main Debian (all packages are built
>> against unstable, not rebuilt when entering testing), but bpo has less
>> eyeballs, I suspect.
>> Oh - and I suspect my example with ffmpeg is a quite valid one: Some
>> cases of undefined img_convert occur at runtime (try install freej in
>> Lenny and then update libav* to the ones from debian-multimedia.org ).
>Well, ffmpeg is a bad example since the devels still refuse to understand the
>meaning and goals of shared libraries and stable ABIs...
Lousy upstream code makes good examples of the kinds of surprises you
can run into when backporting packages.
High quality upstream code would be bad example, as it would support
theory of backporting logic, not shake it.
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Pkg-icecast-devel