> Would you have any objection to getting rid of the actual commands > `sage -clone`, `sage -b <foo>` (just plain `sage -b` would stay of > course), and friends, so that this behavior can be removed? Again, you > could easily do this stuff manually: > > $ cd $SAGE_ROOT/devel/ > $ mv sage vanilla > $ hg clone vanilla sandbox # or just `cp -r vanilla sandbox` > $ ln -s sandbox sage > > I don't think there's that much difference between the above and the > below, to a newbie: > > $ sage -clone sandbox > $ sage -b sandbox
I think you are totally missing the point. To a newbie who has heard of the following: cd mv hg ln you are right. My assumption is that we would like to be as inviting as possible to those who have not. (And they are legion; think of the Windows world...) And yes, probably someone using Sage from the command line is using "cd" at least, but may have just used the command verbatim from the devel guide. Especially having everything be "sage" this and "sage" helps, as does keeping the number of commands to an absolute minimum. That said, if there is a compelling (!) technical reason for getting rid of the cloning procedure as is, and if there is sage -clone (or whatever is appropriate) would just do the commands above automatically, that would be fine. It isn't important *what* the process is, just that it be as transparent as possible. It's not clear why it's so compelling for the Sage directories to live somewhere other than sage/devel; couldn't you make a symlink? ;-) Of course, I may be living in an imaginary world; maybe it's the exception that people become reviewers/developers from a very minimal computer background. My hope would be that we would want to change that. Every person using Sage can become a developer; that's the goal. -- 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