[MacPorts] #21060: installing gdal fails with coreutils+with_default_names

[MacPorts]

#21060: installing gdal fails with coreutils+with_default_names
---------------------------------+------------------------------------------
 Reporter:  jabronson@…          |       Owner:  seanasy@…        
     Type:  defect               |      Status:  new              
 Priority:  Normal               |   Milestone:                   
Component:  ports                |     Version:  1.8.0            
 Keywords:  with_default_names   |        Port:  gdal             
---------------------------------+------------------------------------------

Comment(by seanasy@…):

 Replying to [comment:3 jabronson@…]:
 > Replying to [comment:2 toby@…]:
 > > We really, really need to just remove that stupid variant.
 > Do you mean make "with_default_names" the default when installing
 coreutils, or do you mean don't even allow it as a variant? I assume you
 mean the latter, since the former wouldn't help this bug much, though I'd
 be strongly -1 on removing default names altogether. (What's the point of
 installing coreutils if you have to remember to prefix everything you use
 on a daily basis with a g? It requires totally rewiring your brain, so
 it's just not an option.)

 I'm inclined to agree with toby.  Are we to add complexity to every
 portfile to accommodate gnu coreutils?  It's dangerous to have gnu
 coreutils without the 'g' which is why the variant comes with a warning
 and FreeBSD uses the 'g'.

 Ports should be able to assume coreutils work a certain way and using the
 system versions makes sense.

 Maybe, MacPorts can be modified to use the system utils exclusively.  But,
 I don't think portfiles should be modified to take gnu coreutils into
 account unless MacPorts switches to using only gnu coreutils.

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