On 1/17/12 2:04 PM, Julien Puydt wrote:
Le 17/01/2012 20:54, Jason Grout a écrit :
On 1/17/12 1:38 PM, Julien Puydt wrote:
Le 17/01/2012 15:33, Jason Grout a écrit :
If we separate out twisted on principle, it seems like we should
separate out the other 13 dependent packages that are included.
That's a
maintenance burden I can't take on right now.
Are those heavily patched with respect to upstream?
None, including twisted, are patched with respect to upstream.
Why is there a maintenance burden for pieces of code which upstream
takes full care of?
The maintenance burden is in making and releasing a new spkg for every
single upstream update if we split those off into separate spkgs,
compared to the sagenb spkg automatically downloading and including
necessary dependencies in itself.
Thanks,
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
