[MacPorts] #66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of dependencies? Is there a way to improve upon this?
MacPorts
noreply at macports.org
Thu Dec 15 15:45:20 UTC 2022
#66424: FFmpeg{-upstream} Portfiles seems to have an inordinate amount of
dependencies? Is there a way to improve upon this?
--------------------------+--------------------
Reporter: artkiver | Owner: (none)
Type: enhancement | Status: new
Priority: Low | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: ffmpeg |
--------------------------+--------------------
Comment (by artkiver):
Hi Ken, thank you for replying.
I think we may be contending with a miscommunication?
I am not interested in prebuilt versions and which architectures they are
for, that is not the crux of the issue. Moreover, the CI build system
still has Leopard G4/G5 systems in its tooling, so the fact that FFmpeg
binaries are lacking for aarch64/Apple M1/M2 Silicon (which has now been
out for over two years) while regrettable, seems as if it is also not
relevant to what I wish to focus on in this ticket.
If Rust is needed now, for a number of ports, that also: seems irrelevant.
It is *NOT* necessary to build FFmpeg from source from the upstream
project.
So, that is not meaningful context.
If people need Rust, they should be installing Rust, not FFmpeg.
If people need FFmpeg and there is a variant which has Rust as a
dependency, that variant, should NOT be a default.
Does that make it clearer?
I have already provided an example of a functioning Portfile for FFmpeg
which does not require Rust. I will submit it as a PR for ffmpeg-devel if
conversations continue this way, seeing how jeremyhu (whom I have already
removed as a maintainer for libressl and libressl-devel) and the other
port maintainers are not responding with anything meaningful nor
pertinent. As it currently stands, there are 3 ffmpeg ports in the tree,
when arguably at most there should be two (how is ffmpeg-devel different
than ffmpeg-upstream for example?) and it is conceivable that even those
could be reduced to one with proper use of variants.
--
Ticket URL: <https://trac.macports.org/ticket/66424#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list