[MacPorts] #18149: coreutils +with_default_names vs. gettext vs. MacPorts

[MacPorts]

#18149: coreutils +with_default_names vs. gettext vs. MacPorts
-------------------------------------+--------------------------------------
 Reporter:  macports@…               |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  Normal                   |   Milestone:  MacPorts Future                      
Component:  base                     |     Version:  1.7.0                                
 Keywords:                           |        Port:  gettext, coreutils                   
-------------------------------------+--------------------------------------

Comment(by jmr@…):

 I fixed a handful of this stuff in r45851. There are valid reasons for
 calling out with system/exec sometimes, for example `file delete` doesn't
 handle directories on Panther, and `file link -symbolic` won't let you
 link to a file that doesn't exist. There are still quite a lot of places
 where bare command names are being used, and they should be converted to
 use full paths, preferably as detected by autoconf (and falling back on
 binaryInPath). These are the ones I found:
 {{{
 bunzip2
 chmod
 chown
 curl
 diff
 dscl
 file
 find
 gunzip
 gzip
 id
 lipo
 patch
 tar
 touch
 xcodebuild
 }}}
 At first glance it seems like all of them should be converted so that
 broken ports can't break base. But we should be careful of problems like
 what happened with svn (#15868).

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