where to keep scripts for new software

Question

[ATCG]

When downloading software in a unix system to a bin directory $HOME/bin a new directory containing the scripts is created $HOME/bin/packagedir adding this to the path everytime you download a new package makes the $PATH long and complicated. Would you advice to transfer all the scripts from the original package dir to the $HOME/bin this way all scripts are visible if bin is in the path? Thanks

[WouterDeCoster]

Not really a bioinformatics question, but I'd suggest creating a symlink to $HOME/bin/ This also allows you to keep your downloaded software in another location, or multiple locations, to keep everything tidy.

[ATCG]

Yes,I apologize if this is not within the bioinformatics subject, but it is certainly a fundamental (basic but fundamental) concept also used in bioinformatics.

How can one create a symlink from $HOME/path/to/package to $HOME/bin
Thank you!!

[Joe]

Google “symlinking” or “softlinking”.

[Joe]

I’d add that I think it’s perfectly normal for a PATH to become long and complicated, particularly if you rely on local installs instead of system wide.

A good approach is to have each element of the PATH as a separate export command in one of your dotfiles (commonly .bashrc or .profile). It’s then pretty trivial to excise/rearrange the elements by reordering the exports.