Based on the feedback of a number of users, we have added to .acs/.bash_profile.acs a MODPATH variable to control if ../bin, ../lib, ../etc have to be added to the corresponding paths' environment variables.

The reason for adding ../lib, ../bin and other ../ values to the corresponding environment variables is to allow easy testing of code under development in a module without having to intall it with the "make install" command. In this way, one can simply work in the test or src directory of a module, compile and start applications, clients, and containers that will now automatically use what has just been built.

On the other hand, these relative paths can give some troubles depending on the current working directory and on the specific configuration of the machine you are working on: unexpected shared libraries and executables can be used instead of the standard ones. Also, there could be security issues.

By default .bash_profile.acs assumes that the value is 0 and the paths should not be added. This default has been selected based on requests from a number of developers.

To switch on this behavior

add the following line:
export MODPATH=1

in your $HOME/.bash_profile BEFORE sourcing the standard $HOME/.acs/.bash_profile.acs

To switch off this behavior

Simply unset MODPATH in your $HOME/.bash_profile BEFORE sourcing the standard $HOME/.acs/.bash_profile.acs