On Feb 21, 5:47 am, David Kirkby <david.kir...@onetel.net> wrote: > On 21 February 2011 10:36, Keshav Kini <keshav.k...@gmail.com> wrote: > > > I also wonder why the development guide recommends that we use > > mercurial from inside a Sage session. It seems considerably more > > tedious than just using it from the command line. Is there some > > advantage I'm not seeing? > > > -Keshav > > I would say one advantage is that the version of Mercurial used is > known. If people use their own version, which may be newer or older, > then it can causes issues. It was one of these issues that is holding > back the update of the Mercurial package in Sage. > > It would seem worth putting something to the above effect in the > developers guide, so people know why to use the version in Sage.
Another advantage is for people who have not contributed patches of any kind anywhere, for which the queueing process is difficult to understand. Doing everything from within Sage makes it as self- contained as possible, which enables the occasional developer doing a very small patch (referenced earlier in this thread) to do it without learning extra syntax, but only using the Sage command line. Certainly the devel guide should have info for people who are more advanced, but it is essential to leave this in for those who don't know how to make aliases or soft links or whatever, or know what a PATH is. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
