I'm trying to update my MAFFT version without overwriting the existing version (it's difficult for me to get root access). I've created a pseudo bin folder to contain the new MAFFT files, but I seem to be unable to specify priority of the new MAFFT location (defaults to /user/local/bin). When I do call the new MAFFT version (even when renamed), I receive the following error:
v7.310 != v7.385 (2018/Feb/3) There is a problem in the configuration of your shell. Check the MAFFT_BINARIES environmental variable by $ echo $MAFFT_BINARIES This variable must be *unset*, unless you have installed MAFFT with a special configuration. To unset this variable, type $ unset MAFFT_BINARIES or % unsetenv MAFFT_BINARIES Then retry $ mafft input > output To keep this change permanently, edit setting files (.bash_profile, .profile, .cshrc, etc) in your home directory to delete the MAFFT_BINARIES line. On MacOSX, also edit or remove the .MacOSX/environment.plist file and then re-login (MacOSX 10.6) or reboot (MacOSX 10.7).
Should I change my environment path to include my pseudo bin desktop folder? Won't that still leave a conflict between the original local bin? I'm relatively new to bash and unfamiliar with this sort of problem.