aboutsummaryrefslogtreecommitdiffstats
path: root/misc/py-YABT
ModeNameSize
-rw-r--r--Makefile370logstatsplainblame
-rw-r--r--distinfo127logstatsplainblame
-rw-r--r--pkg-descr478logstatsplainblame
8&id=be0ef99c09cd8633626c8261118a4fb7374d9b30'>fix symlinks for ansible when non-default version is installedlifanov2018-07-241-1/+1 | | | | | | | | | | | | | | | | | | | | | | 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.0lifanov2018-07-021-1/+1 | | | | | | 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 portslifanov2018-05-181-1/+1 | | | | | | | | 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 updatelifanov2018-03-261-2/+1 | | | | | o Remove vanity "Created by:" line o Add upcoming ansible24 port to CONFLICTS * Reduce dependency on the python2 metaportantoine2018-02-191-2/+2 | | | | | PR: 225752 Submitted by: Yasuhiro KIMURA * reinstate sysutils/ansible23lifanov2017-12-011-1/+1 | | | | | PKGBASE collision has been resolved This reverts r455222 * Remove sysutils/ansible23, it clashes with python flavor workantoine2017-12-011-1/+1 | | | | | | Do not add back without checking PKGBASE uniqueness for all flavors first With hat: portmgr * Convert Python ports to FLAVORS.mat2017-11-301-4/+4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464 * update conflicts after addition of sysutils/ansible23lifanov2017-11-301-1/+1 | * sysutils/ansible1: Switch to paramiko (2.x)koobs2017-07-171-1/+1 | | | | | | | | | | | | | | | | | | 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 packaginglifanov2017-04-131-1/+8 | | | | | 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 itlwhsu2016-11-131-1/+6 | | | | build without conflict * Declare this slave port only uses python:2 now that the master portmatthew2016-11-021-0/+2 | | | | | can use python-3. No change to generated package, so no portrevision bump. * Update to 1.9.6matthew2016-04-182-4/+4 | | | | | | | - extend expiry date another month PR: 208896 Submitted by: maintainer (lifanov@mail.lifanov.com) * Update to 1.9.5matthew2016-03-222-4/+4 | | | | | | | | | | - 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 1stmatthew2016-02-261-0/+3 | | | | | | | | 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 submissionmatthew2016-01-231-0/+3 | | | | | | | | | | | | -- 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 thematthew2016-01-131-17/+14 | | | | | | Makefile Pointy hat to me...