Feature request: Non-interactive installation of juliaup without side effects for usage in automated installation script (alternative to --yes)

[omlins]

Motivation

At CSCS, we are developing a new user environment in which we aim to provide the wonderful juliaup rather than a particular version of julia. As for any fully automated software stack installation procedure, all steps must be non-interactive.

Current status

The only option to install juliaup non-interactively is currently using the option --yes, which has some undesired side effects for our use case, namely the modification of ~/.bashrc and ~/.profile (and maybe writing some things into ~/.julia).

Feature request

• Minimal: add option --no-side-effects (or similar), which deactivates the modification of ~/.bashrc and ~/.profile (and writing things into ~/.julia).
• Optimal: expose all parameters that can be set during interactive juliaup installation as command line parameters and enable a non-interactive installation without the option --yes.

Thanks!!!

[davidanthoff]

There is another parameter --add-to-path=no, and I'm fairly positive that should disable the modification of the shell scripts. You then have to put julia and juliaup on the PATH yourself, of course.

You can control into which Julia depot Juliaup puts its config file and then the downloaded Julia versions via the env variable JULIAUP_DEPOT_PATH, so I think if you set that you should be able to prevent anything from going into .julia.

Would those options enable your scenario?