#12229: Add section in the developers manual about sagenb development
----------------------------------------------------+-----------------------
Reporter: jdemeyer | Owner: mvngu
Type: enhancement | Status:
positive_review
Priority: blocker | Milestone: sage-5.2
Component: documentation | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: William
Stein, Jeroen Demeyer, Punarbasu Purkayastha, Karl-Dieter Crisman, Keshav Kini
Authors: Jason Grout, Karl-Dieter Crisman | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------------+-----------------------
Comment (by kini):
To quote my recent comment on #11080:
>John Palmieri, who is sitting next to me at sage days 41, suggests that
we just not package a repository with sagenb at all. What do you think?
After all, sagenb is considered an upstream package at this point, and we
don't package repositories for those. Plus it's using a revision control
system that isn't included with sage anyway (yet). Also, due to various
decisions by people over the lifetime of the repository, the repository is
really large - 14 MB at maximum compression, at the current master. So
removing it would slim down the sage source and binary distributions by a
non-negligible amount. The docs added at #12229 already give instructions
on how to clone the repository from github anyway. So why do we need to
ship a repo?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12229#comment:46>
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.
