On Wed, May 18, 2016 at 5:46 PM, René J.V. <rjvber...@gmail.com> wrote:
> This got me thinking about more elegant ways to avoid the issue, in > particular Debian/Ubuntu's approach of distinguishing "user" packages and > "developer" packages. The former contain everything required to use the > package, other than for development. For ffmpeg this would mean, for > instance, the ffmpeg c.s. executables, and the runtime shared libraries > (libavFoo.x.y.z.dylib and libavFoo.x.dylib). Headerfiles and the linker > library (libavFoo.dylib) are provided by the corresponding -dev package. The problem with this is that if a MacPorts user can't get something from a prebuilt package, you have to force both the "user" and "developer" ports to be installed because any dependents will necessarily be doing linking. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
