+ansible

[ddobrinskiy]

Resolves #300

Stuff we need to do before merging:

• Needs more local testing (blocked by how to use a package locally if not yet merged in pantry? pkgx#427 (comment)) - @ddobrinskiy
• can we add all the bin files in a less hacky way? original question - @mxcl
  • probably good enough for now

[what-the-diff]

• A new project was added to the projects directory.
• The hosts file contains a single host, localhost with ansible_connection=local
• package yml has been created for this project and it is using github tags as version source (versions:github)
• It also defines dependencies on python 3+ and pipenv from pypa/pipenv repo which will be installed in virtual environment during build phase of tea-build process
• Build script creates venv enviroment under {{prefix}}/venv path where all executables are copied into bin folder inside that venv dir so they can be used by other packages without conflicts between different versions of same executable name like 'ansible' or 'ansible-playbook'. This way we have multiple instances of these binaries available at once but only one instance per each binary name is visible outside the virtual environments because those names are registered in TEA registry database when building them via tea-build command line tool

[mxcl]

Possibly symlinks would work. I dunno.

tests prove it works! I say LFG