On Sunday, March 2, 2014 11:11:10 AM UTC-5, Volker Braun wrote: > > On Sunday, March 2, 2014 11:33:22 AM UTC+1, Jeroen Demeyer wrote: > >> The problem is that Sage cannot know in advance that you will *not* move >> the Sage tree. > > > Neither does any other software. If you move an installed program then it > won't work any more, and we shouldn't go around teaching users otherwise. > > Whaa..? That works for the hacker set, but a lot of users on Mac/Windows move programs around all the time. It's a feature. And typically the Mac version works fine (with sage-location) when moving all over the place, and we should expect users to do so for their own convenience. Or am I missing something here?
> For binary distributions we should make all paths relative until it is > installed (so if you compile new stuff it won't be relocatable any more). > Failing that, we could replace the sage starter script with a special > script that updates paths once before copying the old sage script back. > -- 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.
