#6865: [with patch, needs work] Use templates for CSS
-------------------------+--------------------------------------------------
 Reporter:  timdumol     |       Owner:  boothby                 
     Type:  enhancement  |      Status:  new                     
 Priority:  minor        |   Milestone:  sage-4.1.2              
Component:  notebook     |    Keywords:  notebook css stylesheets
 Reviewer:               |      Author:  Tim Dumol               
   Merged:               |  
-------------------------+--------------------------------------------------

Comment(by mpatel):

 Replying to [comment:6 jason]:
 > What is MANIFEST.in and when do we need to add things to it?
 I believe the `sage -bdist` and `sage -sdist` invoke
 [http://docs.python.org/distutils/sourcedist.html#specifying-the-files-to-
 distribute distutils] to build `sage-*.spkg`.  Distutils uses
 `SAGE_ROOT/devel/sage/MANIFEST.in` to determine which files to include in
 the distribution.  If we add files to the local Mercurial repository, we
 should check that some line(s) in `MANIFEST.in` includes the newly tracked
 files or add a new line.  Otherwise, the next (pre-)release of Sage will
 not include them.  As mvngu puts it, this results in
 [http://groups.google.com/group/sage-
 
devel/browse_thread/thread/697693c77e8d7ee8/290f2ec5412b909d?q=repository+corruption+group
 :sage-devel#290f2ec5412b909d "repository corruption"].

 Previous sightings: #4460, #5653, #5799, #6568, etc.

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