On 2025-10-03 06:06, Gregorio Litenstein wrote:
What is the intended use of the different ffmpeg ports?
Given that we currently have ffmpeg, ffmpeg-devel, ffmpeg4 (which
mostly mirrors ffmpeg), and also versions 6, 7 and 8 that install the
libraries to their own versioned folders... is the idea to be able to
use them side-by-side (with the exception of devel and ffmpeg)?
Some ports, like opencv4 have path dependencies on libraries being in
the default old path, which por example mean that building opencv4
will pull ffmpeg, even though there are 3 major version updates available.
I made an issue for this (https://trac.macports.org/ticket/70729) over
a year ago and it's mostly been ignored.
How should we proceed? I can see two ways forward:
1. Mimic what the boost ports are doing, and turn ffmpeg into a stub
port that pulls in one of the others.
2. Add +ffmpeg{version} variants to opencv4 and whichever other ports
might have a similar behavior (I don't know if there's any)
Could I maybe get the maintainers for these ports to weigh in?
I second the request for the maintainers of these ports to weigh in. I
asked a similar question a few weeks ago[1], and got no answer.
Best regards,
—Jim DeLaHunt
[1] email thread "What is up with ffmpeg\* ?"
<https://lists.macports.org/pipermail/macports-users/2025-September/053833.html>
--
. --Jim DeLaHunt, Vancouver, Canada
