[MacPorts] #34271: python27 2.7.3_0 py27-gtk 2.22.0_1 etc -- pkg-config files not installed correctly for python 2.6 and 2.7 versions of pygtk and pygobject

[MacPorts]

#34271: python27 2.7.3_0 py27-gtk 2.22.0_1 etc -- pkg-config files not installed
correctly for python 2.6 and 2.7 versions of pygtk and pygobject
-------------------------------------+--------------------------------------
 Reporter:  stephen.langer@…         |       Owner:  macports-tickets@…                                                                 
     Type:  defect                   |      Status:  new                                                                                
 Priority:  Normal                   |   Milestone:                                                                                     
Component:  ports                    |     Version:  2.0.4                                                                              
 Keywords:                           |        Port:  py25-gtk py27-gtk py26-gtk py27-gobject py26-gobject py25-gobject python26 python27
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):

 * cc: openmaintainer@…, nomaintainer@… (removed)
 * cc: ryandesign@… (added)


Comment:

 Hello, pkgconfig maintainer here.

 The 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.

 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/34271#comment:10>
MacPorts <http://www.macports.org/>
Ports system for Mac OS