Trouble upgrading Macports to Sierra
Brandon Allbery
allbery.b at gmail.com
Thu Mar 30 18:04:08 UTC 2017
On Thu, Mar 30, 2017 at 1:51 PM, Langer, Stephen A. (Fed) <
stephen.langer at nist.gov> wrote:
> This reminds me of something I’ve been wondering about. Why do the
> migration instructions recommend explicitly reinstalling all previously
> installed ports, and then optionally marking the previously requested ports
> as “requested”? Isn’t it simpler to explicitly reinstall only the
> previously requested ports, and let macports figure out the dependencies?
> That way, if the dependencies have changed you only are reinstalling the
> necessary ports and there’s no need to fiddle with the requested status
> afterwards.
That will usually work --- but not always. Often this is because of buggy
dependencies in Portfiles; the only reliable way to catch them is to always
build in trace mode, but that's painfully slow.
--
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: <http://lists.macports.org/pipermail/macports-users/attachments/20170330/4c7d7fda/attachment.html>
More information about the macports-users
mailing list