#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 jhpalmieri):

 Replying to [comment:38 jdemeyer]:
 > And what is your opinion on [comment:34]?

 All things being equal, the answer to all three would be "no". Also, all
 three options for the `sage` command should be considered "advanced"
 options and not widely advertised.

 Since `sage -i` has been the only way to install packages until recently,
 though, I'm not sure all things are equal. Maybe you're right, though, and
 we should encourage using `make pkg`, and after a while, `sage -i pkg`
 will be used less and less, and it can be thought of the same way as `sage
 -b` and `sage --docbuild`.

--
Ticket URL: <http://trac.sagemath.org/ticket/18859#comment:40>
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.

Reply via email to