Thanks. Come to think of it, I started using "sudo make" exactly for the
reason you say, but it never actually occurred to me to draw a clear
distinction for when I should/shouldn't elevate.
On Tuesday, November 7, 2017 at 9:01:53 AM UTC-5, Michael Orlitzky wrote:
>
> On 11/06/2017 09:54 PM, Clay Thompson wrote:
> >
> > Usually when I install from source/devel, I install as root ("sudo
> > make"). But Sage will not allow me to do that.
>
> General advice, not specific to SageMath:
>
> Most software should be built as an unprivileged (i.e. non-root) user.
> It's only when you want to install the result in a location like
> /usr/local that you would need to escalate to root with "sudo make
> install ..."
>
> Root permissions are needed to write to /usr, but they aren't needed to
> read any of the system libraries, or to write the build junk to the
> project directory, or to execute the compiler, etc. By running "sudo
> make", you run the risk of executing any bad code in the project's build
> system as root. (The "make install" could do something bad, too -- but
> that one thing is a lot easier to audit than the entire build system of
> SageMath and its dependencies.)
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
