#6187: [with patch, needs review] After making a clone, the reference manual 
(and
other docs) should not have to be completely rebuilt.
---------------------------+------------------------------------------------
 Reporter:  jhpalmieri     |       Owner:  tba                        
     Type:  enhancement    |      Status:  new                        
 Priority:  major          |   Milestone:  sage-4.1                   
Component:  documentation  |    Keywords:                             
 Reviewer:  John Cremona   |      Author:  John Palmieri, Mitesh Patel
   Merged:                 |  
---------------------------+------------------------------------------------

Comment(by mpatel):

 I've attached new versions of both patches.  Apply only the `v3` pair to
 the indicated repositories.  Changes:

  * `sage-clone` now copies any existing auto-generated `.rst` files to the
 new branch, preserving modification times.
  * `builder.py` now updates the pickle first, since otherwise it always
 regenerates existing `.rst` files after cloning.
  * `jsMath` --> `jsmath` in `sage-clone`.

 It's OK to delete existing auto-generated `.rst` files prior to cloning,
 as long as `doc/output/doctrees/en/reference/reference.pickle` disappears,
 too.  The patches don't cover this case, since I think it occurs rarely in
 practice.  I conjecture that '''most''' of the time, the `update_mtimes`
 line doesn't actually build anything, but I've been wrong before.

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