[MacPorts] #18315: 1.7.0 install hangs on Leopard 10.5.6

[MacPorts]

#18315: 1.7.0 install hangs on Leopard 10.5.6
-------------------------------------+--------------------------------------
 Reporter:  velociraptor@…           |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  Normal                   |   Milestone:  MacPorts Future                      
Component:  base                     |     Version:  1.7.0                                
 Keywords:  postflight, shell error  |        Port:                                       
-------------------------------------+--------------------------------------

Comment(by blb@…):

 Replying to [ticket:18315 velociraptor@…]:
 > As an aside, looking in the process table, the original postflight
 script was being called with:
 > {{{
 > sudo /bin/bash
 /Volumes/MacPorts-1.7.0/MacPorts-1.7.0.pkg/Contents/Resources/postflight
 /Volumes/MacPorts-1.7.0/MacPorts-1.7.0.pkg / / /
 > }}}
 > (that's three trailing slashes)

 Yes, that's how Apple's installer works, it passes
 [http://developer.apple.com/documentation/developertools/conceptual/softwaredistribution/Install_Operations/chapter_8_section_3.html#//apple_ref/doc/uid
 /10000145i-CH14-DontLinkElementID_9 four arguments] to the script, it just
 so happens that the way the install works those three arguments are all
 the root /.

 >
 > b) postflight script errored out when trying to find dep_map_clean.tcl
 upgrade_sources_conf_default.tcl, due to $TCLSH and $PACKAGE_PATH
 variables not being set properly.  I hard-coded in these for the
 appropriate path to get the postflight script to run after copying the
 package to a read/write location.

 TCLSH is set in postflight itself, to /usr/bin/tclsh, so I'm not sure why
 that wouldn't be set properly; PACKAGE_PATH comes from Apple's installer
 like the arguments on the command line so running postflight manually
 means it won't be set unless you set it.  Though running it manually was,
 as jmr said, just a workaround in 1.6.0 and isn't meant to be run that way
 now.

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