#9433: Put more files under revision control.
-----------------------------+----------------------------------------------
   Reporter:  jhpalmieri     |       Owner:  tbd         
       Type:  enhancement    |      Status:  needs_review
   Priority:  major          |   Milestone:  sage-4.6    
  Component:  distribution   |    Keywords:              
     Author:  John Palmieri  |    Upstream:  N/A         
   Reviewer:                 |      Merged:              
Work_issues:                 |  
-----------------------------+----------------------------------------------

Comment(by leif):

 Replying to [comment:53 jhpalmieri]:
 > Replying to [comment:49 leif]:
 > > Ok, except that {{{hg_script}}} won't work if {{{$SAGE_ROOT}}}
 contains spaces,
 >
 > Since this script only gets run once, by the release manager when this
 ticket is merged, and since it doesn't get distributed with Sage, I'm not
 going to worry about it.

 Yes, this is (and was meant) a non-issue, I only mentioned it for
 completeness. ;-)

 > > and "sage" should be "Sage" in the messages,
 >
 > I'll fix that.  You mean messages like "Error building the sage source
 code package" or  "Error copying sage root repository", right?

 Yes.

 > > Btw, why aren't base packages subject to upgrading? (I would have
 expected the root spkg there.)
 >
 > I'm not sure what you mean by "base packages".

 The packages /files in {{{spkg/base}}}, also referred to by {{{$(BASE)}}}
 in the Makefile ({{{deps}}}).

 > The {{{sage-upgrade}}} script will certainly upgrade the sage-root spkg.

 Yes, of course. ({{{sage-update}}} currently doesn't attempt to upgrade
 anything from {{{spkg/base}}}.)

 > Should I create an upgrade path on sage.math?  I may wait a day or two
 for the disk situation to settle down...

 I have no opinion on that.

 > Re the "pipestatus" command, I'm going to leave it as is and see what
 happens during testing.  (When I tested a month ago or so, the sage-root
 spkg got upgraded, and I vaguely remember checking that the log file had
 the right name, but I'll test again.)

 This again just referred to ''spaces in SAGE_ROOT''. (My last suggestions
 would work with such.)

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