[MacPorts] #23762: InsightToolkit should use python26 variant

MacPorts noreply at macports.org
Thu Feb 18 17:49:22 PST 2010


#23762: InsightToolkit should use python26 variant
------------------------------------+---------------------------------------
  Reporter:  jeremyhu@…             |       Owner:  dweber@…           
      Type:  request                |      Status:  closed             
  Priority:  Normal                 |   Milestone:                     
 Component:  ports                  |     Version:  1.8.2              
Resolution:  fixed                  |    Keywords:                     
      Port:  InsightToolkit         |  
------------------------------------+---------------------------------------

Comment(by dweber@…):

 OK, looks like a consistent change that will not break anything.

 Out of curiosity, I've noticed a change to {{{set pyLib ...}}} in the
 {{{proc setPython}}} section, i.e.:

 {{{
     575 proc setPython { {major 2} {minor 6} } {
     576     global pyVer python pyPort pyBin pyLib pyInc pyFrame pySite
     577     set pyVer       ${major}.${minor}
     578     set python      python${pyVer}
     579     set pyPort      python${major}${minor}
     580     set pyFrame
 Library/Frameworks/Python.framework/Versions/${pyVer}
     581     set pyLib       ${pyFrame}/Python
     582     #set pyLib       lib/${python}
     583     set pyBin       bin/${python}
     584     set pyInc       include/${python}
     585     set pySite      lib/${python}/site-packages
     586     if [string match "2.6" ${pyVer}] {
     587         # python2.6 is a true framework installation; whereas
 installs for 2.4
     588         # and 2.5 contain symlinks in the framework path to the
 prefix path; and
     589         # those symlinks can break the file_map stage of port
 activation.
     590         set pyBin   ${pyFrame}/bin/${python}
     591         set pyInc   ${pyFrame}/include/${python}
     592         set pySite  ${pyFrame}/lib/${python}/site-packages
     593     }
     594 }
 }}}


 I don't know how to track when or who made that change.  Is there an svn
 command to track a change for a specific section of the file?  (I don't
 know of any.)

 If you run {{{ls -l /opt/local/lib/python*}}}, you get similar results for
 2.3 - 2.5, and a different result for 2.6.

 Again, there are differences from 2.4-2.5 vs. 2.6 when you run

 {{{
 $ ls -l /opt/local/Library/Frameworks/Python.framework/Versions/2.?/lib/
 /opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/:
 total 4.0K
 lrwxr-xr-x 1 root wheel 24 Oct  2 15:04 python2.4 ->
 /opt/local/lib/python2.4/

 /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/:
 total 4.0K
 drwxr-xr-x 3 root admin 102 Oct 22 17:37 pkgconfig/
 lrwxr-xr-x 1 root wheel  24 Feb 10 09:23 python2.5 ->
 /opt/local/lib/python2.5/

 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/:
 total 28K
 -rwxr-xr-x   2 root wheel  20K Jun 24  2009
 libpyglib-2.0-python2.6.0.dylib*
 lrwxr-xr-x   1 root admin   31 Jun 24  2009 libpyglib-2.0-python2.6.dylib
 -> libpyglib-2.0-python2.6.0.dylib*
 -rwxr-xr-x   2 root wheel 1.3K Jun 24  2009 libpyglib-2.0-python2.6.la*
 drwxr-xr-x   6 root admin  204 Feb  8 15:04 pkgconfig/
 drwxr-xr-x   3 root wheel  102 Oct 16 16:59 pygtk/
 drwxr-xr-x 631 root admin  21K Oct 27 15:42 python2.6/
 }}}


 This is why the {{{setPython}}} proc in the InsightToolkit port handles
 the paths differently for 2.6.

 (Maybe this should go into the 'new' ticket.)

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


More information about the macports-tickets mailing list