[MacPorts] #42188: Dependency error in ffmpeg 2.1.3_1 on libogg 1.3.1_0

[MacPorts]

#42188: Dependency error in ffmpeg 2.1.3_1 on libogg 1.3.1_0
----------------------+----------------------
  Reporter:  me@…     |      Owner:  devans@…
      Type:  defect   |     Status:  closed
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.2.1
Resolution:  invalid  |   Keywords:
      Port:  ffmpeg   |
----------------------+----------------------

Comment (by larryv@…):

 Replying to [comment:13 me@…]:
 > IME Apple bug reports are useless, so I won't bother.

 That’s fine, because there is no Apple bug here.

 > MacPorts could give a warning when DYLD_LIBRARY_PATH is set.

 MacPorts is not invoked in any way when you use a port; it only manages
 dependencies and installation.

 > It would help if there were a reference for DYLD_LIBRARY_PATH that
 > more clearly stated not just what it does but what it should and
 > should not be used for.

 The `dyld(1)` man page does mention one use case, which is more or less
 the //only// use case.
 {{{
 DYLD_LIBRARY_PATH
        This  is  a  colon  separated  list  of directories that contain
        libraries. The dynamic linker searches these directories  before
        it  searches  the default locations for libraries. It allows you
        to test new versions of existing libraries.
 }}}
 Common sense suggests that prepending to the default library search path
 can easily cause shadowing problems. Imagine a program that added
 `/usr/local/bin/foobar` to the beginning of your `$PATH`; now imagine that
 that directory contained broken versions of `bash`, `ls`, `ssh`, and so
 on.

 Setting `DYLD_LIBRARY_PATH` is analogous to prepending to `$PATH`; setting
 `DYLD_FALLBACK_LIBRARY_PATH` is kind of like appending to `$PATH`.

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