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

Comment(by jhpalmieri):

 Replying to [comment:136 jdemeyer]:
 > Why not simply avoid `hg clone` in `sage-make_devel_packages`?  If the
 other spkgs can be made without using `hg clone`, surely the same should
 work for the `sage_root` spkg?

 It certainly could be done, but it makes the repo harder to maintain.
 Suppose you want to add a new file to the repo.  If you clone, you just
 run "hg add" (or apply a patch which accomplishes this) and you're done.
 If you manually copy everything over, as is done for the other repos, then
 you also have to modify sage-make_devel_packages, maybe root-spkg-install,
 maybe sage-sdist.  This is especially true for the root repo, where files
 need to be dealt with individually: it's not like the Sage repo where
 except for a handful of files, you just copy over an entire directory
 (devel/sage/sage/), and it's not like the scripts repo where except for a
 handful of files, you just copy over everything with a certain name
 ("sage-*").

 Maybe instead it could run "hg manifest" and then manually copy over the
 listed files.  But this seems really awkward when "hg clone" does exactly
 what is required.

 > Version 1.7.3 of Mercurial was merged in sage-4.6.2.alpha2, ticket
 #10594. It can still be unmerged if you think that's a good thing to do.
 Then we would fall back to Mercurial 1.6.4.

 I'm really not sure about this.  Perhaps it should be discussed on #10594.
 The lack of backwards compatibility seems problematic to me.  I can try to
 post something there later today.

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