Can you sage -bdist a copy of sage that you don't have write permissions to? If you can, this would give you a tarball that you could then unpack in your home directory that shouldn't have any references to the original.
- Robert On Aug 6, 2009, at 5:17 AM, VictorMiller wrote: > > Georg, Thanks. My situation is a bit unique (as William fully > understands). Copying the sage source from sagemath.org is not an > option that I have. Our sysadmins get the source and then build it > and make a built directory available to us on the system. I have to > proceed from there. > > Victor > > On Aug 6, 7:02 am, gsw <georgswe...@googlemail.com> wrote: >> On 5 Aug., 19:15, VictorMiller <victorsmil...@gmail.com> wrote: >> >> >> >> >> >>> Ok, I think I've found the problem. Perhaps this should point to >>> the >>> need for making clear and complete instructions about creating your >>> own copy. >> >>> I found that in my local copy there was a sage script that >>> pointed to >>> the systemwide sage. When I changed that I now get my local >>> copy. So >>> perhaps the instructions should say: >> >>> Copy the whole directory tree. Inside the top level directory there >>> is a script called sage. Edit that so that SAGE_ROOT points to your >>> local copy, and use that version of sage to run sage (e.g. by >>> making a >>> symbolic link to it in one of your local directories in search order >>> ahead of the system wide copy). >> >>> So, another question -- it seems that sage -ba didn't regerenate the >>> individual doc files, since if I do something like >> >>> EllipticCurve?? >> >>> the path that it displays is in the systemwide directories. Should >>> sage -ba do that? How do I regenerate these files? >> >>> Victor >> >> Hi Victor, >> >> a) >> Just to be sure --- this sounds like the "Guess 1" from William >> (second message in this thread) turned out to be 100% correct, or >> am I >> missing something? >> And if "Guess 1" was correct, how could we have phrased it better / >> more understandable? >> >> b) >> Regarding the EllipticCurve?? issue. Sorry for asking --- but did you >> do "sage -ba" again, after having adressed the $SAGE_ROOT problem? >> >> c) >> Generally speaking, the way of "copying" an existing Sage tree, and >> then starting to develop, is a way rarely used. So there might be >> lurking even more pitfalls yet to be discovered. >> On the other hand, building Sage from source is spectacularly easy: >> >> - download the single tar file with all sources for the current Sage >> release from sagemath.org >> - unpack the tar file in the directory of your choice >> - cd into the newly created "Sage root" directory (after possibly >> moving and/or renaming it, if you wish so) >> - type "make" (and wait a few hours) >> >> You then have the setup / the environment Sage is developed in, and >> where certainly fewer such issues as you report are to be expected. >> And *if* any problems should occur during the build/install as >> described above, it's likely that they will be sorted out even >> faster, >> once reported here to sage-devel. >> >> Cheers, >> Georg > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
