#33489: MPlayer @1.0rc4 - hidden dependencies ----------------------------+----------------------------------------------- Reporter: hans@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: wontfix | Keywords: Port: MPlayer | ----------------------------+----------------------------------------------- Comment(by hans@…):
Regarding that comment, the "let autodetect do its magic" part means that explicit {{{--enable-foo}}} or {{{--enable-foo=/opt/local}}} do not do the right thing with (ancient) mplayer's ./configure. To enable a feature you really do need to remove the --disable-foo flag but just let ./configure autodetect that foo is present, instead of adding --enable-foo like you do in normal autoconf'd programs. But the removing of --disable- foo only happens inside variant blocks where the necessary depends are added
I believe a comment like this should be present in the Portfile to explain it to the innocent Portifle reader.
ffmpeg is odd since it used to always use a private internal copy and not link against the system version... In fact in comment 2 I don't see ffmpeg listed there. Are you sure it was complaining about ffmpeg and not just opencore-amr?
Yes you, are right. It does not depend on ffmpeg (as installed by the ffmpeg port). It links (statically, probably) against its own copy of ffmpeg. -- Ticket URL: <https://trac.macports.org/ticket/33489#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS