Jeroen Demeyer <jdeme...@cage.ugent.be> writes: > On 2012-03-09 06:18, Keshav Kini wrote: >> - Make `sage -b` also run `sage --python devel/sagenb/setup.py develop`, >> copy relevant files from devel/sagebin to local/bin/ , and copy >> relevant files from devel/sageext/ to... somewhere, perhaps share/sage/ ? > Thereby complicating the development process of SCRIPTS and EXTCODE for > no good reason.
The point is to eventually have scripts and extcode be in the same repository, along with the library. Also, I don't see how anything is more complicated. Just do `sage -b` after you save a file. This is the same thing you already do when hacking the Sage library. If anything, it becomes more consistent this way. I'm sure most developers are used to having to build their code after editing it anyway. > Moreover, what if I want to hack the very script that > does "sage -b"? What if you want to hack the script which does `sage -sdist`? What if you want to hack the script which does `sage -hg`? What if you wanted to hack sage-env? I don't see that anything really becomes more difficult than it already is. Concretely speaking, if you wanted to hack sage -b and its current behavior was not even sufficient to successfully copy your new version of the script into local/bin/ (which strikes me as being pretty unlikely to happen in practice), you could always just copy it manually that one time. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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
