<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Mar 4, 2015 at 12:39 PM, Chris Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hmm, I did not realise this. I thought that it was the opposite way around, so only files explicitly registered are made visible. Whats the reason it doesn't work this way ? Some technical limitation or by choice (for some reason I don't yet see) ?</blockquote></div><br>For one example, MacPorts has neither control over Apple-provided files nor guaranteed lists of such files for all OS X versions. Even if you whitelist e.g. /usr/lib/*.dylib, what stops Apple from burying a reference to something somewhere else in one?</div><div class="gmail_extra"><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>