On Wed, Mar 4, 2015 at 12:39 PM, Chris Jones <[email protected]> wrote:
> 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) ? 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? -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
