#4261: [with patch, needs work] sympow Configure fails to handle aliases
--------------------+-------------------------------------------------------
 Reporter:  wjp     |        Owner:  mabshoff  
     Type:  defect  |       Status:  new       
 Priority:  major   |    Milestone:  sage-3.2.1
Component:  build   |   Resolution:            
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by was):

  * summary:  [with patch, needs review] sympow Configure fails to handle
              aliases => [with patch, needs work] sympow
              Configure fails to handle aliases

Comment:

 REFEREE REPORT:

 1. It does not fail is rm is an alias.  It gives the original executable
 with an exact path.
 {{{
 teragon-2:sympow-1.018.1.p5 wstein$ alias rm="rm -i"
 teragon-2:sympow-1.018.1.p5 wstein$ which rm
 /bin/rm
 teragon-2:sympow-1.018.1.p5 wstein$ RM=`which rm`
 teragon-2:sympow-1.018.1.p5 wstein$ echo $RM
 /bin/rm
 }}}

 So I totally don't get what the problem is.  The above patch would have
 the effect of making it so the scripts would annoyingly suddenly actually
 *be* interactive if one has aliased rm to "rm -i".

 So from my point of view, it looks like this patch introduces a bug
 instead of fixing one.

 2. This patch would replace all the absolute paths to programs to their
 names, thus completely removing whatever "upstream's" point was in having
 those variables.  That's suspicious.

 So I'm dubious.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4261#comment:5>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to