[MacPorts] #17998: Linking to Python 2.5 framework is broken due to broken symlinks

[MacPorts]

#17998: Linking to Python 2.5 framework is broken due to broken symlinks
--------------------------------------------+-------------------------------
 Reporter:  evert.rol@…                     |       Owner:  mww@…           
     Type:  defect                          |      Status:  new             
 Priority:  Normal                          |   Milestone:  Port Bugs       
Component:  ports                           |     Version:  1.6.0           
 Keywords:  python boost framework symlink  |        Port:  python25        
--------------------------------------------+-------------------------------

Comment(by mleinart@…):

 Looks like my patch has some bad side effects - other packages (py25-*,
 likely others) install in /opt/local/lib/python2.5/site-packages which is
 now not an absolute path.  Ports seems to get confused when adding the
 files in there to file_map after activation and errors out with "Error:
 Target org.macports.activate returned: Not a directory" - this leaves the
 package installed and activated, but the files are stranded and not listed
 in 'port contents'.  I'm guessing this is the reason that
 /opt/local/lib/python2.5 was moved to be the real directory and
 /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
 the symlink.

 Unless someone wants to fix all of the ports installing in
 /opt/local/lib/python*/site-packages/, it looks like the symlink of
 libpython25.a in Mac/Makefile (in the Python2.5 source) needs to be
 patched to be absolute instead of relative.

 I haven't looked at the other lang/python* ports - do they all move this
 lib/python2.5 directory from where Python's Makefiles install and re-
 symlink?

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