#11926: "make build" should run Sage once
------------------------+---------------------------------------------------
   Reporter:  jdemeyer  |          Owner:  GeorgSWeber   
       Type:  defect    |         Status:  needs_review  
   Priority:  major     |      Milestone:  sage-4.7.3    
  Component:  build     |       Keywords:  Makefile build
Work_issues:            |       Upstream:  N/A           
   Reviewer:            |         Author:  Jeroen Demeyer
     Merged:            |   Dependencies:                
------------------------+---------------------------------------------------

Comment(by leif):

 s/succesfully/successfully/

 Still, running `sage` (especially the full bunch of shell scripts) there
 is quite dangerous, as almost everything can happen.  Worse, there's no
 ''"DO NOT INTERRUPT THIS"''*, and error messages aren't even logged.

 Better write some `install` target (and / or a `sage-first_time` script),
 and update the Sage Installation Guide, especially with respect to files
 that are created upon first start-up, hardcoded path etc. etc.

 IMHO we should in general do certain things ''upon installing Sage'' (some
 actually ''during'' the build), rather than checking them and doing them
 ''for the first time'' when someone tries to start Sage.


 ----
 * This message is btw. printed too late, as `install_moved()` already does
 some stuff before the script (eventually!) gets to this.

 [[BR]]

 P.S.: No serious sysadmin builds in, say, `/usr/local/`, or leaves an
 "installation" in `/tmp/`.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11926#comment:16>
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