Hi Joey, On 06/18/2010 03:38 AM, Joey Hess wrote: > resolved immediately in either of two ways; by moving chromium to > experimental until ffmpeg reaches unstable, or moving ffmpeg 0.6 to > unstable now. I've seen no rationalle given against doing either.
html5 works with the ffmpeg experimental version, I don't see any particular reason to move chromium in experimental, and as far as I know ffmpeg maintainers will move ffmpeg0.6 to unstable after squeeze release. > (For that matter, there's no particular reason not to link chromium against > its internal ffmpeg copy, given that it's being blocked from reaching > testing.) I'm trying to understand if chromium can be maintained in a stable release (squeeze), and indeed, given the bad security history[1] of ffmpeg, we can ship chromium linked against its internal ffmpeg copy. [1]http://security-tracker.debian.org/tracker/source-package/ffmpeg Cheers, Giuseppe.
signature.asc
Description: OpenPGP digital signature
