On Wed, Aug 14, 2013 at 7:28 AM, John Cremona <[email protected]>wrote:
> On 14 August 2013 14:20, Volker Braun <[email protected]> wrote: > > IMHO we shouldn't support this (i.e. moving the sage install around). > Just > > fail with an error message that you moved the sage install tree, you > need to > > rebuild (make distclean && make) before continuing. It doesn't have > anything > > to do with Sage really, usually if you compile something and then move > the > > object directory around then it won't work because of rpaths in shared > > libraries. > > > > Fair enough, I will just have to remember in future. My habit until > recently was to build all versions (including bet and rc versions) in > my home directory, and then when offical releases came out I would do > the same and then copy into /usr/local and change ownership & > permissions. What I might do now is the same for beta and rc versions > (which I only want locally anyway), build the official releases in > /usr/local directly, and if I want to, make a copy of those in my home > You could do sudo su mkdir /usr/local/sage chown cremona. /usr/local/sage/ chmod a+rx /usr/local/sage cd /usr/local/bin/ ln -s /usr/local/sage/current/sage . and do all your building and deployment directly in /usr/local, but without ever doing sudo again for this. Just make sure to do the following once you want a particular version to be the default systemwide. cd /usr/local/sage ln -s sage-5.11 current > directory. That will work since I see no problem sometimes having as > my own development copy a build with rpaths linking back to > /usr/local/. Provided that the development work does not invlove > testing new spkgs, anyway... > > John > > > We can still support binary distributions. Making the binary distribution > > involves rewriting all paths to be relative. For "make bdist" we can then > > require the presence of additional tools to rewrite rpaths. > > > > > > On Wednesday, August 14, 2013 12:22:36 PM UTC+1, John Cremona wrote: > >> > >> Deleteing or renaming the original build does not solve it, not does > >> rebuilding the sage library (sage -ba). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sage-support" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/group/sage-support. > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
