William Stein wrote: > There's also a "make install" option, after you complete the build. > You have to set the environment variable DESTDIR to the target directory, > then type "make install". We needed this for the Debian package. > > It's not coupled so much. The only coupling is that the file > SAGE_ROOT/sage has the location sage is installed in listed near > the top. That file then sets the environment variable SAGE_ROOT, > which is then used by the rest of SAGE. > > One can build SAGE anywhere, move it anywhere else, and run it once, > and it will adapt to being in the new location. (Spaces in the path > are dangerous though...) > > -- William
William, This is all great news. I didn't realize sage had been modified to respect DESTDIR. If that is the case, all is good. I'm doing a compile on my machine to check on a few things, but essentially, we should be able to make a simple ebuild that will: 1) download sage source distro 2) run make 3) run make install to portages image directory 4) portage will copy sage to /opt/sage 5) in the post install section of the ebuild, we will call sage once to start it up and let it fix its current path Presto! We have sage installed and managed by portage (of course we're not using much of the management). Once I verify it compiles on my system (which it should), I'll put that ebuild together and give it a whirl. Regards, Mark --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
