swig-python and python{24,25,31,32}

Lawrence Velázquez larryv at macports.org
Sun Jan 4 18:58:21 PST 2015

On Jan 4, 2015, at 3:46 PM, Michael Dickens <michaelld at macports.org> wrote:

> That said, ports that -rely- on swig-python will probably need to be
> rev-bumped, because they will have a library/libraries linked against
> the Python library of choice. Once the old Python has been replaced_by
> the new one, the linkage of the generated swig-python libraries will be
> invalid; rebuilding those ports should do the trick, I think.

But how will those dependent ports know what to link against? The old Pythons will be replaced, but users' `port select` selections are not going to be migrated.


More information about the macports-dev mailing list