Due to the way Rocket have decided to add shebangs to the top of Python scripts (wrongly in my opinion but that's another story) I have tried to re-install miniconda.  During the initial install it asked for the location of Python, however, on the re-install it doesn't and uses the original value supplied.

How to I change that initial value?​​

Hi Pete,
I don't think that "decided to add shebangs to the top of Python scripts" is an appropriate and correct statement. Shebang is essential part of UNIX scripts. More, if you take a look at Miniconda scripts for Linux, you will find the same shebangs.
Miniconda installer doesn't ask Python's location, because Python is shipped within Miniconda and it will be install to the installation directory, along with other packages. If you want to re-install Miniconda, you should run the same command "./miniconda-zos-<build_details>.run --path <installation_dir>". If the installer detects that specified directory contains a Miniconda instance, you will be asked to confirm the update: Updating Miniconda distribution at '<installation_dir>'. Continue? [y/N]

​

---

Due to the way Rocket have decided to add shebangs to the top of Python scripts (wrongly in my opinion but that's another story) I have tried to re-install miniconda.  During the initial install it asked for the location of Python, however, on the re-install it doesn't and uses the original value supplied.

How to I change that initial value?​​

Hi Tatiana

​My comment about shebangs was "Due to the way Rocket have decided to add shebangs " not the fact that there are shebangs  I don't see why the Python location has to be hardcoded when a much more generic #!/usr/bin/env python3 could be used.

However, that is not my current problem.  We don't use Python from Rocket.  My initial install didn't use the Rocket version either, I pointed the install at a different location.  I now want to change that location.  How do I do that?  The initial location must have been stored somewhere to pick it up again during the re-install.

---

Due to the way Rocket have decided to add shebangs to the top of Python scripts (wrongly in my opinion but that's another story) I have tried to re-install miniconda.  During the initial install it asked for the location of Python, however, on the re-install it doesn't and uses the original value supplied.

How to I change that initial value?​​

You might want to address this question to Anaconda developers outside of Rocket, who introduced this architecture. However, hard-coded paths to Python can be found not only in the shebangs, but also in scripts bodies.

At the moment Miniconda can work only with the Rocket's Python, which is shipped with Miniconda installer. Could you give us a bit more information how you installed Miniconda initially? Exact commands would be helpful.

---

Due to the way Rocket have decided to add shebangs to the top of Python scripts (wrongly in my opinion but that's another story) I have tried to re-install miniconda.  During the initial install it asked for the location of Python, however, on the re-install it doesn't and uses the original value supplied.

How to I change that initial value?​​

​Hi Tatiana

​It looks like I misunderstood the point of the shebang entries in the python scripts inside miniconda.  I now realise that miniconda is using the Python that comes with the install package.

The problem I now have is the target for the installation.  This directory is used to create the paths inside of the scripts.  This means that in my organisation we would have to have all the LPARs where we use miniconda to be installed to use the same path names (it would have to be supplied from a central point).  With over 150 LPAR that is just not going to be possible.

Therefore, we are going to have to revert to a single central location and deny our regional teams the ability to install the software they require themselves.  Hardly an improvement on the previous method of installation.

I have read your documentation on copying installations to multiple LPARs and will have to follow that. ​

---

Due to the way Rocket have decided to add shebangs to the top of Python scripts (wrongly in my opinion but that's another story) I have tried to re-install miniconda.  During the initial install it asked for the location of Python, however, on the re-install it doesn't and uses the original value supplied.

How to I change that initial value?​​

Hi Pete,

Even before miniconda, many of our ported tools were sensitive to their install location (as Unix tools in general do).

With different locations on each LPAR, how was it implemented before miniconda? Were different teams installing software themselves, or were you installing it on a single system and then somehow adapting the installation on each LPAR to its new location?

Thanks,
Vladimir

---