Hi
hacking/env-setup does not work for me. I’m on a Mac with a previous installation of Ansible via homebrew. The cause is easy to spot, but I’m wondering if there is a specific reason why it is setup in this way.
Before running env-setup:
which ansible > /usr/local/bin/ansible
echo $PATH > /Users/magnus/google-cloud-sdk/bin:/usr/local/bin:/usr/local/share/npm/bin/:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
I have ansible at the end of my path env variable.
Running env-setup:
PATH=/Users/magnus/Documents/Programmering/Magnusart/ansible/bin:/Users/magnus/google-cloud-sdk/bin:/usr/local/bin:/usr/local/share/npm/bin/:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
which ansible > /usr/local/bin/ansible
Since the hacking env-setup prefixes the path instead of postfixing the current installation of ansible is still active.
Looking in env-setup it prefixes the PATH with the path to the development instance of ansible, is there a particular purpose for this?
/Magnus