Bug#654984: libav: Please use a less confusing package name

[Reinhard Tartler]

On Mon, Jan 9, 2012 at 10:01 AM, IOhannes m zmoelnig <zmoelnig at iem.at> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2012-01-07 21:47, Paul Gevers wrote:
>>>
>>> It was specifically design for migration purposes. Still, you might
>>> want to update the dependencies for your package and update it to use
>>> '/usr/bin/avconf' instead of '/usr/bin/ffmpeg'.

Fabian is right, I meant to write '/usr/bin/avconv' of course.

>> If I understand correctly (I have not yet looked at the real content of
>> the libav package) you are providing a /usr/bin/ffmpeg binary (for now).
>> That seems fine with me, and I will let my upstream know that for Debian
>> the way to go is /usr/bin/avconf. I assume other distributions are doing
>> the same, lets try to make sure we stay in sync as much as possible
>> (although we might be leading the way
>
> wouldn't using an alternative/diversion of /usr/bin/ffmpeg to
> /usr/bin/avconv be a good idea?
> even if "ffmpeg" is not going to be packaged as such within the
> foreseeable future?

In order to not break existing scripts, the (now named) libav-tools
package ships both /usr/bin/ffmpeg as well as /usr/bin/avconv. The
former is deprecated and conserves the old behavior, while the new one
provides a more consistent command-line interface.

The utility /usr/bin/ffmpeg may go away in future libav releases.

>
> iiuc, libav is meant as a _replacement_ of ffmpeg, so i don't see a
> compelling reason to wipe out all traces of the former package.

Both libav as a project as well as I as packager both take the
migration path seriously.


-- 
regards,
    Reinhard