Brian, So Per the documentation:
http://docs.ansible.com/ansible/latest/intro_installation.html#running-from-source I decided to go ahead and build from source, because it says there in the documentation: "Once running the env-setup script you’ll be running from checkout and the default inventory file will be /etc/ansible/hosts. You can optionally specify an inventory file (see Inventory <http://docs.ansible.com/ansible/latest/intro_inventory.html>) other than /etc/ansible/hosts:" so following that: deniz@lemtmp]$ git clone https://github.com/ansible/ansible.git --recursive Cloning into 'ansible'... remote: Counting objects: 265907, done. remote: Compressing objects: 100% (17/17), done. remote: Total 265907 (delta 13), reused 2 (delta 2), pack-reused 265888 Receiving objects: 100% (265907/265907), 87.31 MiB | 769.00 KiB/s, done. Resolving deltas: 100% (170839/170839), done. [deniz@lemtmp]$ cd ansible/ [deniz@lemansible]$ ls CHANGELOG.md Makefile bin lib test CODING_GUIDELINES.md README.md contrib licenses ticket_stubs CONTRIBUTING.md RELEASES.txt docs packaging tox.ini COPYING ROADMAP.rst docsite_requirements.txt requirements.txt MANIFEST.in VERSION examples setup.py MODULE_GUIDELINES.md ansible-core-sitemap.xml hacking shippable.yml [deniz@lemansible]$ source ./hacking/env-setup running egg_info creating lib/ansible.egg-info writing lib/ansible.egg-info/PKG-INFO writing dependency_links to lib/ansible.egg-info/dependency_links.txt writing requirements to lib/ansible.egg-info/requires.txt writing top-level names to lib/ansible.egg-info/top_level.txt writing manifest file 'lib/ansible.egg-info/SOURCES.txt' reading manifest file 'lib/ansible.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' warning: no files found matching 'SYMLINK_CACHE.json' writing manifest file 'lib/ansible.egg-info/SOURCES.txt' Setting up Ansible to run out of checkout... PATH=/private/tmp/ansible/bin:/private/tmp/ansible/test/runner:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/usr/local/Cellar/python3/3.6.1/bin/python3:/Users/deniz/Code/Go/bin:/usr/local/Cellar/go/1.8.3/libexec/bin PYTHONPATH=/private/tmp/ansible/lib: MANPATH=/private/tmp/ansible/docs/man: Remember, you may wish to specify your host file with -i Done! [deniz@lemansible]$ ls /etc/ansible ls: /etc/ansible: No such file or directory So it is not there despite what the offical doc is saying....Any ideas ? On Thursday, October 19, 2017 at 7:44:28 AM UTC-7, Brian Coca wrote: > > That is a brew specific problem, they DO create ansible.cfg but they > choose to use different directories. > > > ---------- > Brian Coca > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/8f1b2945-5389-4d8c-8673-79e9428a4094%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
