Dear Arshpreet,
On 2012-05-18, arshpreet singh <
ars...@gmail.com> wrote:
>> If you want a system wide installation, make the symbolic link in
>> /usr/local/bin, i.e. "cd /usr/local/bin" and "ln -s
>> /directory/to/sage-installation/sage sage". Then you can start sage by just
>> typing "sage" anywhere.
> Thanks it worked :)
>
>>(on my system Sage is located in /opt/sage).
>
> is there any good thing to install sage in particular directory(like
> /opt/sage)? as i made a directory sage in my home folder and compiled
> from
source.is it also right way-,please correct me if i am wrong?
It is (at least partially) a matter of taste. For example, I always
build Sage in an "ordinary" folder in my home directory, not in /opt/
or /bin/ or so.
Also, I do not put it Sage my PATH: I don't want that the command "sage"
starts Sage, because I have different versions of Sage on my computer,
and so I always go to the location of a particular Sage version and
start it locally with ./sage (note the "./").
Other people would perfer to be able to launch Sage globally on the
machine. Then, you could put the sage starter script into
/usr/local/bin/, for example.
By that, I mean the following:
- Build sage (could be in any folder, let's call it SAGE_ROOT; and
could be build from source or by extracting a pre-built binary)
- In the folder SAGE_ROOT, there is a file called "sage". Open it with
any text editor.
- You will see the following at the top:
# Set SAGE_ROOT to the location of the sage install, i.e. the directory
# containing this shell script. If unset, we will try to figure it out
# automatically.
#SAGE_ROOT=/path/to/sage-version
- Remove the "#" from the previous line, and replace
/path/to/sage-version with the correct value, i.e., with the absolute
path to the folder in which you have built sage.
- Save the changes, and then copy the script into (for example)
/usr/bin/. Then, the command "sage" should start Sage.
Will different people work on your computer, or will you be the only
one?
Best regards,
Simon