Good! Now here is a question I have been waiting to ask: We know know that it is Not A Good Idea to build Sage in one place and move it, so when I install Sage system-wode on the machines I administer, which I only do for full releases (not betas etc), I have been building it where I want it (in /usr/local/sage) and then switching /usr/local/bin/sage which is a symlink to point to the new version.
Now with the new build system I could, but would prefer not to, build from scratch for this purpose, but would like to go in to my /usr/local/sage/ build, pull the new master and rebuild. BUT if I do that then while the new version is building it will be unavailable to users, which is not ideal. Am I missing something simple? What do other people who manage systems with several users do or plan to do? John On 30 January 2014 21:29, Harald Schilly <harald.schi...@gmail.com> wrote: > On Thu, Jan 30, 2014 at 10:08 PM, Volker Braun <vbraun.n...@gmail.com> wrote: >> Source tarball is here (to be uploaded to the mirrors): > > Cool! I've already started to move it to the mirrors. > > Harald > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-rele...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
