I was looking to download some tool and it said to update your PATH variable, but I thought
/usr/bin was the "standard".
It is not too uncommon to have tools that expect to be installed at user level. As such, they will not assume that you can modify anything directly under
/usr. It is often common, however, to have a
~/usr/bin directory where you can include symlinks to tools that you have installed for your user. Such that you don't have to constantly update a
I sometimes feel that it is more efficient to add a symlink from /usr/bin (or /bin or /usr/sbin or one of the friends) to wherever the application installed put the programs, rather than to add the program to a PATH definition.
- Don't need to update PATH settings in potentially a plethora of places.
- Fewer directories to search.
- This makes for a non-standard installation, which means you need to consider the impact on things like updates and re-installation, particularly when those may be carried out on people other than yourself.
The program will work the same whether its directory is added to the PATH, the files are copied into a directory already part of the PATH, or symlinked from an included directory to the directory where it is installed.
In Ubuntu ~/.profile includes:
# set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi