#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Ralf Stephan
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/kcrisman/ticket/16030 | e5ebea680cc3281acb9761d625d23426a6ebdb54
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
It should be clear that you won't get very far if you can't compile Sage.
The "Rebuilding Sage" section already links to the install guide.
I disagree with you presenting "sage -dev" as an equal alternative. Having
two competing ways to achieve the same thing is a shitty UI. People read
the manual because they want to know what is recommended, not what one
could also do but later learns that most developers don't do. PEP 20:
"There should be one-- and preferably only one --obvious way to do it."
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:54>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
