<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, May 18, 2016 at 5:46 PM, René J.V. <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.</blockquote></div><br>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.<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>