#9644: Make Sage run even when $SAGE_ROOT contains spaces
----------------------+-----------------------------------------------------
   Reporter:  mpatel  |       Owner:  jason
       Type:  defect  |      Status:  new  
   Priority:  major   |   Milestone:       
  Component:  misc    |    Keywords:       
     Author:          |    Upstream:  N/A  
   Reviewer:          |      Merged:       
Work_issues:          |  
----------------------+-----------------------------------------------------

Comment(by leif):

 Ok, it could perhaps be documented in more prominent places, but it's
 (still) twice in {{{$SAGE_ROOT/README.txt}}}, the second time a bit to
 mild:
 {{{
 ...
 MORE DETAILED INSTRUCTIONS TO BUILD FROM SOURCE
 -----------------------------------------------
 ...
 3. Extract the Sage source tarball and cd into a directory with no
    spaces in it. [...]

 ...

 RELOCATION
 ----------

 You *should* be able to move the sage-x.y.z directory anywhere you
 want. If you copy the sage script or make a symbolic link to it, you
 should modify the script to reflect this (as instructed at the top of
 the script). It is best if the path to Sage does not have any spaces in
 it.
 ...
 }}}

 And afair it is (or at least has been at some time) better documented in
 the Installation Guide.

 So I would open two tickets (one could be this with changed title):

  * Make sure {{{$SAGE_ROOT}}} does not contain spaces, e.g. in {{{sage-
 env}}} (blocker).

  * Improve documentation (CAPSLOCK? Add/move remarks to top of files.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9644#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
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