On Friday, May 1, 2015 at 10:08:21 AM UTC-7, Volker Braun wrote: > > If it weren't in the path then you would have to run "make" whenever you > want to change one of the scripts in src/bin. This gets boring real quick. >
I see. Sloppy but convenient if you happen to be working on the scripts. How attainable are cleaner solutions? hardlink the files? put these files under source control in local/bin so that src/bin isn't necessary at all? Given that all the other stuff (including .py library files, for which "make" is also just copy operation) does need "sage -b" or some flavour of "make", it's really quite surprising to see anything in src/ take precedence during execution over local/ . (there really should be a subtarget "make install-scripts" that only does the required copy operation, in which case the boredom would set in a little later) Another solution that would leave sage in a cleaner state in general would be to only add src/bin to the path when you're working on the scripts, (the git log on src/bin indeed suggests that this doesn't happen too often). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
