Changes between Initial Version and Version 1 of Ticket #34271, comment 10


Ignore:
Timestamp:
Jan 8, 2013, 11:53:46 PM (11 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34271, comment 10

    initial v1  
    33The reason the Python 2.5 (and earlier) versions in MacPorts install directly into /opt/local/lib/pkgconfig is because they are not framework builds. Python 2.6 and later are framework builds in MacPorts, and therefore install their files into the deep directory you mentioned earlier. Understanding how or why Python 2.5 and earlier do what they do is not very useful since Python 2.4 is already being deleted and 2.5 is hopefully not far behind. The way Python 2.6 and later are built is the way we want Python built in MacPorts going forward.
    44
    5 I think the correct solution is what you already mentioned in the description you don't want to do: set PKG_CONFIG_PATH properly. If you want to find Python 2.6 bits, set PKG_CONFIG_PATH to include Python 2.6's pkgconfig directory, etc. It's up to each port to do this, because it's up to each port to know which version(s) of Python it wants. We might conceivable reduce the burden on port maintainers by making a portgroup to automate that but we don't have one to do that right now.
     5I think the correct solution is what you already mentioned in the description you don't want to do: set PKG_CONFIG_PATH properly. If you want to find Python 2.6 bits, set PKG_CONFIG_PATH to include Python 2.6's pkgconfig directory, etc. It's up to each port to do this, because it's up to each port to know which version(s) of Python it wants. We might conceivably reduce the burden on port maintainers by making a portgroup to automate that but we don't have one to do that right now.