#11106: Make location of notebook style files configurable
-----------------------------+----------------------------------------------
   Reporter:  flint          |          Owner:  jason, mpatel, was          
       Type:  enhancement    |         Status:  positive_review             
   Priority:  minor          |      Milestone:  sage-4.7.2                  
  Component:  notebook       |       Keywords:  notebook, style, sd31       
Work_issues:                 |       Upstream:  N/A                         
   Reviewer:  Burcin Erocal  |         Author:  Achim Fassbender, Rado Kirov
     Merged:                 |   Dependencies:                              
-----------------------------+----------------------------------------------

Comment(by rkirov):

 Replying to [comment:9 jdemeyer]:
 > Replying to [comment:8 rkirov]:
 > > not sure if I should be answering this, but i am guessing it will
 become a separate spkg. Is there an obvious problem with this?
 >
 > Rado, do you mean a new spkg in addition to the existing "sagenb" or
 will it be inside "sagenb"?
 >
 > There is no problem with this but I think it is something that you
 really should think about.  As I mentioned on
 [http://groups.google.com/group/sage-
 release/browse_frm/thread/758ac9a5106f5d4f], I would like the flask
 notebook to be ''either''
 >
 > (a) 100% part of Sage, in which case it is simply a set of patches on
 Trac
 > which should be merged in the usual way by the Sage release manager.
 >
 > (b) 0% part of Sage, i.e. a completely separate project with a separate
 release manager and a separate bug tracker which will give me a complete
 spkg to be merged into Sage.
 >
 > I believe that anything between these two extremes would create extra
 complications.  Currently, option (a) holds for sagenb.
 > I would not find it a problem if it starts out as (b) in the development
 phase but once it's merged it reverts back to (a), i.e. part of Sage.
 >
 > Also keep in mind that a few tickets deal mostly with the Sage library
 but still need patches to sagenb, so maybe (a) would be a slightly better
 solution.  Recent examples: #9976, #10052.

 reply in sage-release not to pollute the ticket.

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