[MacPorts] #12429: port cannot handle spaces in various variables

MacPorts noreply at macports.org
Mon Aug 31 04:00:07 PDT 2009


#12429: port cannot handle spaces in various variables
-------------------------------+--------------------------------------------
  Reporter:  nox@…             |       Owner:  macports-tickets@…                   
      Type:  defect            |      Status:  reopened                             
  Priority:  High              |   Milestone:  MacPorts Future                      
 Component:  base              |     Version:  1.7.0                                
Resolution:                    |    Keywords:                                       
      Port:                    |  
-------------------------------+--------------------------------------------

Comment(by ryandesign@…):

 Replying to [comment:10 giorgio_v@…]:
 > Is this bug still reproducible with the 1.8 release?

 Yes. Take this minimal portfile:

 {{{
 PortSystem 1.0

 name foo
 version 1.0
 worksrcdir "${distname}/Path with spaces"

 pre-fetch {
     return -code error "${worksrcpath}"
 }
 }}}

 {{{
 $ port fetch
 MacPorts running without privileges. You may be unable to complete certain
 actions (eg install).
 Portfile changed since last build; discarding previous state.
 --->  Computing dependencies for foo
 MacPorts running without privileges. You may be unable to complete certain
 actions (eg install).
 --->  Fetching foo
 Error: Target org.macports.fetch returned:
 /mp/var/macports/build/_private_tmp/work/{foo-1.0/Path with spaces}
 Error: Status 1 encountered during processing.
 }}}

 There should not be curly brackets around the worksrcdir in the message.

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


More information about the macports-tickets mailing list