Migration issue

Daniel J. Luke dluke at geeklair.net
Thu Jan 12 21:41:38 CET 2017

On Jan 12, 2017, at 4:08 PM, Adam Dershowitz <dersh at alum.mit.edu> wrote:
> But, if there are actually any ports that I have where +universal is the default, and is necessary, that would break them, and their chain of dependancies.  I don’t know if there are any like that, or how I can tell, except by manually reviewing info for each one.  Is there any other way?
>>> One option would be to uninstall everything and then to avoid the migration script, and just to reinstall my list of requested ports and see what happens.  But, that will take some time.  

I would do this - (if you had done it back when you suggested it, you would probably be already done and not having to think about this anymore by now).

>>> Especially, since a good number of ports end up building from source instead of binaries.  But, it could be that the reason for this is that they ended up being +universal, so they were not available on the buildbots.

if you just deactivate everything - anything that already built (or you got a binary for) will be fast to reinstall (assuming the variants match).

if you really wanted to, you could also set up your own binary archive (https://trac.macports.org/wiki/howto/ShareArchives2)

Daniel J. Luke

More information about the macports-users mailing list