On 1/17/12 1:44 AM, Jeroen Demeyer wrote:
On 2012-01-16 23:36, jason-s...@creativetrax.com wrote:
Please vote:
[ ] Yes, remove the twisted spkg and include twisted in the sagenb spkg
as a dependency
[X] No, keep the twisted spkg as a separate spkg
I dislike putting everything into one big spkg. Having some separation
looks cleaner to me. What if we *do* need to patch Twisted in the
future, what's the procedure for that?
We can include the patch in the sagenb spkg, in a patches directory,
that is then applied to the twisted source there.
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.
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
