#18859: Update docs to use "make pkgname" instead of "./sage -i pkgname"
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.9
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers: Ralf Stephan
Report Upstream: N/A | Work issues: ???
Branch: | Commit:
u/jdemeyer/update_docs_to_use__make_pkgname__instead_of____sage__i_pkgname_|
626113afdc2a3023f2ce1e83fa8d0123cbae442f
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
> Yes, and `./sage -i` will keep working exactly like before, which I
consider a good thing (keeping in mind backwards compatibility). Why do
you consider that a bad thing?
If it still works like before, why do you change all occurrences of 'sage
-i' in the source and doc?
> Well, I don't think that running `make foo` is inherently more
complicated than running `sage -i foo`.
It is. If you just say "type 'make pkgname'" in a doc/exception message, I
am 100% sure that people will open terminals, type what they are requested
to type, and not know what to do with the message "There is no Makefile in
this folder" just because they are not in SAGE_ROOT.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18859#comment:28>
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.
