Remove expired ports:

2017-10-01 sysutils/ansible1: please upgrade to sysutils/ansible
sysutils/bsdploy, depends on expired sysutils/ansible1
sysutils/py-ploy_ansible, depends on expired sysutils/ansible1

update sysutils/ansible to 2.8.2

This creates sysutils/ansible27 port for users that wish to stay on
Ansible 2.7 stable branch.

https://github.com/ansible/ansible/blob/v2.8.2/changelogs/CHANGELOG-v2.8.rst

update sysutils/ansible* ports

sysutils/ansible: 2.7.1
Changes:
https://github.com/ansible/ansible/blob/v2.7.1/changelogs/CHANGELOG-v2.7.rst

sysutils/ansible26: 2.6.7
Changes:
https://github.com/ansible/ansible/blob/v2.6.7/changelogs/CHANGELOG-v2.6.rst

sysutils/ansible25: 2.5.11
Changes:
https://github.com/ansible/ansible/blob/v2.5.11/changelogs/CHANGELOG-v2.5.rst

All ports: move default configuration directory back to LOCALBASE/etc/ansible as
before the flavors conversion. Configuration is version-specific and not
Python-specific
and this is a more intuitive location.

PR:		232377
Reported by:	Tomoyuki Sakurai (default configuration path)

update sysutils/ansible to 2.7.0

This is a major release. Please see changelog and migration guide:

https://github.com/ansible/ansible/blob/2.7/changelogs/CHANGELOG-v2.7.rst
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html

This also introduces sysutils/ansible26, which will track the 2.6 stable
branch.

fix symlinks for ansible when non-default version is installed

The issue is that before stage, other binaries are links to ansible:

bin/ansible-vault -> bin/ansible
bin/ansible-playbook -> bin/ansible

During stage, these get renamed with a suffix, like 3.6, but the
target of the symlink doesn't change:

bin/ansible-vault-3.6 -> bin/ansible
bin/ansible-playbook-3.6 -> bin/ansible

This either creates broken links if the package for the default
Python version is not installed or it creates links to the
wrong binary if it is.

Thank you Andreas Sommer for the fix!

PR:		229960
Submitted by:	Andreas Sommer

update sysutils/ansible to 2.6.0

This also introduces sysutils/ansible25 port to track 2.5 release branch.

Changes:
https://github.com/ansible/ansible/blob/v2.6.0/changelogs/CHANGELOG-v2.6.rst

add tests and FLAVORS to Ansible ports

Most of the work was done by koobs. Thank you!

PR:		228268
Submitted by:	koobs
Reported by:	Christopher Hall

sysutils/ansible* - prepare for sysutils/ansible update

o Remove vanity "Created by:" line
o Add upcoming ansible24 port to CONFLICTS

Reduce dependency on the python2 metaport

PR:		225752
Submitted by:	Yasuhiro KIMURA

reinstate sysutils/ansible23

PKGBASE collision has been resolved
This reverts r455222

Remove sysutils/ansible23, it clashes with python flavor work
Do not add back without checking PKGBASE uniqueness for all flavors first

With hat:	portmgr

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

update conflicts after addition of sysutils/ansible23

sysutils/ansible1: Switch to paramiko (2.x)

Follow up of ports r445996. This was missed due to seperate original commits
[1][2] with no PR: references and insufficient QA on my part which would have
picked it up.

This fixes the second packaging error after ports r445866 due to conflicting
paramiko1/paramiko ports, because of:

- sysutils/py-ploy_fabric -> sysutils/py_ploy -> security/paramiko
- sysutils/py-ploy_fabric -> devel/py-fabric -> security/paramiko1 (r445866)
- sysutils/bsdploy -> sysutils/ansible1 -> security/py-paramiko1 (this fix)

 [1] https://svnweb.freebsd.org/changeset/ports/425687
 [2] https://svnweb.freebsd.org/changeset/ports/425989

PR: 214379

sysutils/ansible1: fix packaging

Also, bump expiration date again since I touched it.
I plan to keep it around until sysutils/py-ploy_ansible is migrated.

Change RUN_DEPENDS back to py-paramiko 1.x, for making ports depends on it
build without conflict

Declare this slave port only uses python:2 now that the master port
can use python-3.  No change to generated package, so no portrevision
bump.

Update to 1.9.6
  - extend expiry date another month

PR:		208896
Submitted by:	maintainer (lifanov@mail.lifanov.com)

Update to 1.9.5
 - extend deprecation period by 3 months.  The plan is to expire the
   port about 6 months after the last upstream release.

ChangeLog:
https://raw.githubusercontent.com/ansible/ansible/v1.9.5-1/CHANGELOG.md

PR:		208200
Submitted by:	maintainer (lifanov@mail.lifanov.com)

Deprecate and set expiry for June 1st

Users should migrate to sysutils/ansible, now that ansible 2.x is the
principal release version.

PR:		207491
Submitted by:	lifanov@mail.lifanov.com (maintainer)

Fix default low-level command submission
  -- on FreeBSD root's default shell (/bin/csh) would fail to
     understand the /bin/sh syntax ansible issues.

Import the fix from upstream.

PR:		206498
Submitted by:	matthew
Approved by:	lifanov@mail.lifanov.com (maintainer)
Obtained
from:	https://github.com/ansible/ansible/commit/8647fdc7f25ba1c707c5333ca1581a1fa0ffe566

Ooops.  Commit the Makefile, not the patchfile that should create the
Makefile

Pointy hat to me...

Upgrade ansible to 2.0.0

Provide an ansible1 slave port with ansible-1.9.4 as there are
incompatible changes between ansible-1.9.4 and ansible-2.0.0

Add note in UPDATING

PR:		206174
Submitted by:	lifanov@mail.lifanov.com (maintainer)