[MacPorts] #31132: MacPorts:

[MacPorts]

#31132: MacPorts:
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  Low                      |   Milestone:                                       
Component:  ports                    |     Version:  2.0.2                                
 Keywords:                           |        Port:  MacPorts                             
-------------------------------------+--------------------------------------
 The privilege de-escalation code now used in MacPorts 2 seems to have
 broken the fixup code in the MacPorts port:

 {{{
 --->  Configuring MacPorts
 DEBUG: Using compiler 'Mac OS X gcc 4.0'
 DEBUG: Executing proc-pre-org.macports.configure-configure-0
 Fixing your MacOSX10.5 installation by copying libtclstub8.4.a to
 /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Tcl.framework/Versions/8.4/libtclstub8.4.a
 Error: Target org.macports.configure returned: xinstall: Unable to create
 new file for:
 /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Tcl.framework/Versions/8.4/libtclstub8.4.a,
 Permission denied
 DEBUG: Backtrace: xinstall: Unable to create new file for:
 /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/Tcl.framework/Versions/8.4/libtclstub8.4.a,
 Permission denied
 }}}

 The obvious first try to fix this was to set `configure.asroot yes` inside
 the `if` clause before it attempts to copy into the library into the SDK,
 but this fails; it seems `configure.asroot` must be set before the
 configure phase even begins, so by pre-configure time it's too late.

 The workaround I used was to temporarily add `configure.asroot yes` to the
 main part of the Portfile and run it once, then remove that line again. Or
 I could have just manually fixed things. Since this is just a one-time
 fixup operation, and only needed for people building MacPorts disk images,
 it's obviously not a big deal. If nobody thinks of an easy fix, this
 ticket at least documents the issue and the workaround.

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