If $SAGE_SUDO is set, use it whenever we do "make install" of a package.

[mkoeppe]

That would be a solution for those who want to install Sage in a prefix that's only writable by root.

In this way, building can take place in unprivileged user account.

It could perhaps also be enabled by ./configure --enable-sudo-install. (not on this ticket)

This ticket makes routine changes to all spkg-install scripts. Whenever installing has more steps than just make install, it moves the install part to a separate script spkg-do-install.

*** See #21726 for a slightly different approach ***

CC: @jdemeyer @kiwifb @embray @nexttime @vbraun @mezzarobba

Component: build

Reviewer: Matthias Koeppe, Samuel Lelièvre

Issue created by migration from https://trac.sagemath.org/ticket/21537

[mkoeppe]

Description changed:

--- 
+++ 
@@ -2,5 +2,8 @@
 
 In this way, building can take place in unprivileged user account.
 
+It could perhaps also be enabled by `./configure --enable-sudo-install`.
+
 This ticket requires routine changes to all `spkg-install` scripts.
 
+

[mkoeppe]

Branch: u/mkoeppe/if__sage_sudo_is_set__use_it_whenever_we_do__make_install__of_a_package_

[mkoeppe]

New commits:

444fd6e

Add SAGE_SUDO for packages A-L

[mkoeppe]

Commit: 444fd6e

[kiwifb]

comment:4

Practical matters:

• documentation
• If you need a password and that the time between sudo-ing is longer than the time out, you will have to insert the password quite a number of times. In the case of a parallel install, will it block output to screen until you have entered the password?

I don't know enough of the mechanics of sage standard output on screen to know how requesting a password will affect the flow.

[kiwifb]

comment:5

I guess I should say in the case of parallel make. In which the parallelism of make is translated into installing packages concurrently.

[mkoeppe]

comment:6

Yes, these issues need addressing in documentation and/or implementation.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

666fb57

Add SAGE_SUDO for packages L-P

[sagetrac-git]

Changed commit from 444fd6e to 666fb57

[mkoeppe]

comment:8

Replying to @kiwifb:

In the case of a parallel install, will it block output to screen until you have entered the password?

I don't know enough of the mechanics of sage standard output on screen to know how requesting a password will affect the flow.

The problem of parallel output and prompts has been discussed before in #20884, #21082.
Also #21539 could help.

[sagetrac-git]

Changed commit from 666fb57 to ec6ce24

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

ec6ce24

spkg-do-install: Make executable

[sagetrac-git]

Changed commit from ec6ce24 to 23e3ddc

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

23e3ddc

Packages P-S

[sagetrac-git]

Changed commit from 23e3ddc to 74fbeff