Bug#792619: transition: ffmpeg
andreas.cadhalpun at googlemail.com
Fri Jul 17 11:31:04 UTC 2015
On 17.07.2015 08:57, Andreas Beckmann wrote:
> Andreas Cadhalpun wrote:
>> (The command line tools transition is not required to happen in lock step,
>> because the transitional package libav-tools-links can satisfy the
>> dependencies, until the packages are updated.)
> and from the wiki page:
>> To facilitate the transition, a libav-tools-links package, which
>> 'Provides: libav-tools' and contains links from the av* to the ff*
>> binaries is going to be built from src:ffmpeg.
> That sounds very fragile. Apt does not handle upgrades from real to
> virtual packages very well,
I'm aware of that, but thanks for pointing it out anyway. ;)
> you should use a real transitional package
> named 'libav-tools' (which could just depend on libav-tools-links).
> (See 'apt does not find an upgrade path' bugs from the last years ...)
Now that it's been decided to drop the libav source package after the
transition, we could do this, but the question is, whether we should.
I've asked for feedback about that :
"Though I'm wondering now, if it wouldn't be better to also take over the libav-tools
binary package (instead of the libav-tools-links package), so that existing
installations of libav-tools get migrated to ffmpeg.
The libav-tools-links only 'Provides: libav-tools' so that dependencies can be satisfied,
but since apt prefers real packages over virtual ones, it wouldn't affect existing
What do you think?"
The thing is that last time people didn't like to get the libav tools, when
they had installed ffmpeg...
In any case, this does not have to be entangled with the library transition.
More information about the pkg-multimedia-maintainers