Thank you!  I will try something like this.

On Mon, Sep 4, 2017 at 2:21 AM, John Cremona <[email protected]> wrote:

> On 4 September 2017 at 07:53, Pstrang Rzekle <[email protected]> wrote:
> > Installation Guide for 8.0, Section "3.7 Installation in a Multiuser
> > Environment"
> > and also here:
> > http://doc.sagemath.org/html/en/installation/source.html#
> installation-in-a-multiuser-environment
> >
> > erroneously inform the reader how to install in a system-wide or
> multi-user
> > environment.
> >
> > Following Step 3. "Using your normal user account, build Sage.", then
> Step 4
> > says:
> >
> > Make a symbolic link to the sage script in /usr/local/bin: "ln -s
> > /path/to/sage-x.y/sage /usr/local/bin/sage"
> >
> > Really? Since the "/path/to/sage-x.y/sage" is still in your normal user
> > account, no other "multiuser" can execute the sage script.
>
> No, you can change the permissions there so all can read and execute.
> But see below
>
> >
> > Can anyone properly share the process to install for a
> > system-wide/multi-user environment?
>
> This is what I do:
>
> I create a directory /usr/local/sage owned by my normal username
> (which of course has to have sudo privileges).  Everything happens in
> there.  In that directory I have 2 sage builds from source, in
> separate directories called sage-1 and sage-2, and a symbolic link
> sage-current from one of those (the current one) say
> /usr/local/sage/sage-1 is linked from /usr/local/sage/sage-current.
> After building a new sage in /usr/local/sage/sage-1 I make all that
> directory read/executable by all using chmod -r a+rX.  Meanwhile
> /usr/local/bin/sage is set (once and for all) to be a link to
> /usr/local/sage/sage-current/sage.
>
> Now when I want to build a new sage without breaking the current one
> even temporarily for users, I use the second directory (say sage-2)
> for that.  When done and tested I just move the link sage-current to
> point to sage-2 instead of sage-1, and users automatically get the new
> version.  Next time round, the roles of sage-1 and sage-2 are
> reversed.
>
> This does use up space of course (on one machine my old 7.6 build is
> using up 11G while the current 8.0 uses 9.4G).  You could of course
> empty out the non-current directory, but then building the new version
> will take longer.
>
> There may be cleverer ways of doing things but this works for me.  Of
> course, I have yet another sage directory under my home directory for
> development work which does not touch /usr/local/sage at all.
>
> >
> > Which executables are actually needed?  Should I copy the entire 'local'
> > directory to someplace like /opt/SageMath?  Then what commands to change
> > owner/group and permissions from my normal user?  I don't want to 'chmod
> > 755' everything.
> >
> > Thank you!
> >
> >
> >
> >
> > --
> > 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 https://groups.google.com/group/sage-support.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-support/jIGS_J5_huk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to