Closed htmlboss closed 5 years ago
If this is going into production. I would look at using the global setting of creating custom scripts in /etc/profile.d. This will ensure that all accounts system and user specific get to access the same applications. For development, people should be able to use their .bashrc or .bash_profile so that they can either try new applications or use newer debugging tools.
The /etc/environment from what I can see is used by applications to define certain environment variables. On a Ubuntu VM my /etc/environment file contains two lines a PATH and JAVA_HOME definition. I would prefer the /etc/profile.d way.
Instead of editing the installing user's
~/.bashrc
, we will add a script to/etc/profile.d/
. This will fix cases where multiple users wish to use a single installation and the miniconda path isn't set.I'll be testing this change in a VM.
@dwayne-hart There's 2 schools of thought for global environment variables. There's the method I'm using, and there's also something about
/etc/environment
. Thoughts?