Rocket ported tools (incl. conda) are open sourced. Although you can always learn the code, you are absolutely don't need to! If you want to see, which environment variables were modified, you can run the following commands and compare outputs:
> env | sort #prints out current environment settings
> conda activate <env_name> #activates an environment and adjusts environment settings
> env | sort #prints out new environment settings
You are even not obliged to modify general config files (like /etc/profile). You can run "./<installation_path>/etc/profile.d/conda.sh" command manually, when you want to work with conda in your current session.
In terms of history, I find conda even much more convenient that the old way. Just one command "conda list" shows you all the installed packages with their versions and build numbers. So you don't need to guess where you should gather information which builds you are using.
I have the target directory (filesystem) with git and all it's components. I found the xxx.sh to configure the profile and now need to find the time to collect each of those files into a consolidated file and then add it to my /etc/profile (initially for testing to my ~/.profile. I hope to get to that this weekend.
Thank you for all your help.
Btw. The xxxx.sh files use a variable for the conda directory and it would be easier in this case if the variable were resolved when creating the xxxx.sh files.
I'll update this weekend or early next week on my progress.
Lionel B. Dyck <sdg><
"Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden