Rename ffmpeg package to libav

Bug #820117 reported by llogan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ffmpeg (Ubuntu)
Opinion
Low
Unassigned

Bug Description

Natty and Oneiric appear to be using source from libav instead of FFmpeg. The ffmpeg package (and not just the source package as it is now) should be renamed to libav. I believe the general user believes they are using ffmpeg from FFmpeg instead of libav when the install the "ffmpeg" package. Renaming the package to the proper name would clarify this.

Also, the homepage for the ffmpeg package in Natty is still ffmpeg.org instead of libav.org which is misleading (unless I'm wrong about it being from libav).

Revision history for this message
Reinhard Tartler (siretart) wrote :

Do you think fixing the homepage field warrants a stable release update? I don't think so, as this issue seems rather cosmetic to me. Please reopen this issue if you disagree.

As for the binary package 'ffmpeg', well, the package name is unchanged because:
 - it still installs the main binary into /usr/bin/ffmpeg
 - a lot of other packages declare a dependency on the package 'ffmpeg'.

The next major libav release will bring a new binary that also has a changed command line interface. At that point, a package rename makes sense.

Changed in ffmpeg (Ubuntu):
importance: Undecided → Low
status: New → Opinion
Revision history for this message
zimbatm (zimbatm) wrote :

One year later, libav is still distributed as "ffmpeg" and I think it's still misleading. Libav is a fork of ffmpeg and it seems logical to me that it should have it's own package. Both projects have their own strengths but if you don't want to distribute ffmpeg anymore you just need to make it clear by renaming the package and add a virtual package that points to libav. The /usr/bin/ffmpeg name clash could also be resolved by using the apt-alternative mechanism.

Both projects are good projects and deserve recognition. By mixing the names up it just makes things harder for both to get good user reports on bugs since the versions and codes don't match.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.