port upgrade outdated order

[Brandon Allbery]

On Wed, Mar 4, 2015 at 12:39 PM, Chris Jones <jonesc at hep.phy.cam.ac.uk>
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
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150304/9c47812c/attachment.html>