[MacPorts] #50694: ffmpeg: issues updating to version 3.0

[MacPorts]

#50694: ffmpeg: issues updating to version 3.0
-------------------------------------------------+-------------------------
  Reporter:  devans@…                            |      Owner:  devans@…
      Type:  defect                              |     Status:  new
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.3.4
Resolution:                                      |   Keywords:
      Port:  baresip cmus ffmpegthumbs FreeRDP   |
  goldendict gpac libdlna libextractor           |
  libquicktime-devel mlt moc OpenSceneGraph      |
  pHash py27-bob-io-video transcode VLC wxsvg    |
  xine-lib xmms2 yorick-av                       |
-------------------------------------------------+-------------------------

Comment (by rjvbertin@…):

 Replying to [comment:7 devans@…]:

 > With respect to support multiple versions of ffmpeg, we do.  ffmpeg is
 the current stable version and remains so until a major update occurs (as
 in this case).  ffmpeg-devel is the unstable version which contains the
 newest changes and may or may not be API/ABI compatible with ffmpeg.
 However, it allows those who wish to work on future compatibility to do
 so.

 Well, that's not exactly what I meant, and I doubt you missed that. foo
 and foo-devel ports are typically mutually exclusive alternatives that may
 or may not be true drop-in replacements for each other. I've had the
 opportunity to interact with FFMpeg devs a couple of years ago, and there
 were a couple of people there who were very much convinced of the well-
 foundedness of their choices. It wouldn't surprise me if some of the
 removed APIs never got a (workable) replacement. I cannot assess to what
 extent this is really the case and to what extent dependent ports might
 have good reasons to stick to the older API for the time being, or even if
 there are user-facing changes in the command line utilities that could
 make someone want to stick with the 2.8.6 version.
 I just think it's a win-win situation if you can set up ffmpeg and ffmpeg-
 legacy (or ffmpeg-previous or whatever) ports that can be installed
 concurrently with only some trivial hacking and insignificant/negligible
 maintenance overhead.

 > Since you're the maintainer of VLC, I really haven't looked too closely
 at the current MacPorts version other than to note that it fails to build
 with ffmpeg 3.0.  I didn't really expect you to fix the issue (unless you
 want to) as that is really the job of the upstream developers but was
 hoping that you could help by raising the issue with them.  Since the
 current version of VLC on MacPorts is out of date, it may just be an issue
 of bringing the port up to the latest stable version.

 This has come up before: I'm listed as a maintainer because I submitted a
 port update to VLC 2.2.1 ; it was never my intention to maintain the
 outdated version my port was supposed to replace, esp. since my main
 interest is in libVLC . Not the VLC app itself, which I think one best
 installs from the official installer, also given its flaky build system
 and Videolan's attitude towards MacPorts.
 I'll try to find some time to bump my port to 2.2.2 though so you can
 check whether it supports FFMpeg 3.0 .

 I'll also have to check my proposed Audacity port but IINM that project
 ships a compatible version FFMpeg that we could allow it to use if push
 comes to shove.

-- 
Ticket URL: <https://trac.macports.org/ticket/50694#comment:9>
MacPorts <https://www.macports.org/>
Ports system for OS X