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

 > > So why don't you just change the behaviour of the current command
 'sage -i' so that it installs packages with dependencies?
 > I already answered this: for backwards compatibility and to not add
 unneeded complexity to that command.

 I do not think that backward compatibility matters here. If the behaviour
 of `sage -i` becomes something that the users should not call anymore,
 then it is better to change its behaviour so that they can keep calling
 it.

 > > This would mean that the user interface does not need to be changed.
 > I don't get this...
 >
 > This ticket changes absolutely no interface, only documentation.

 By 'user interface' I mean 'what the users should call'. If you change the
 errors messages and the doc to tell the users to call something else, then
 surely our "interface with the users" changes.

 > To understand each other better, could you please answer the following
 questions with yes/no:
 > Should ./sage -b also build the dependencies of the Sage library?
 Not the subject here.
 > Should ./sage -docbuild ... also build the dependencies of the
 documentation?
 Not the subject here.
 > Should ./sage -i package ... also build the dependencies of package?
 Yes
 > If the answer is not 3 times the same, I would like to know the reason.

 Is it really a problem for you if one command takes dependencies into
 account and not the others? If it is, it is not for me and the users
 probably do not care: among those three commands, they only run the third.

 > The whole point of this ticket is that make package should be considered
 the default way of installing packages. So dependencies are taken into
 account by default.

 And for this reason it would be better, in order to *not* change our
 users's custom, to change what they have to call (`sage -i`) but rather to
 change the behaviour of that command (`sage -i`) so that it does what you
 want, i.e. take dependencies into account.

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