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 to 2.0.0
- Use PORTVERSION over DISTVERSION
- Update minimum RUN_DEPENDS versions
- Seperate OPTIONS from OPTIONS_DESC's
Changes: 2.0.0 - 2015-03-05
* Add support for http proxies
* Deactivate pkg's auto update feature by default
* Add support for firstboot-freebsd-update (disabled by default)
* [BACKWARDS INCOMPATIBLE] switched from ipfilter to pf
Note: you MUST convert any existing ipnat_rules to the new pf_nat_rules.
* Provide defaults for VirtualBox instances (less boilerplate)
* Set full /etc/ntp.conf instead of trying to fiddle with an existing one.
* Support configuration as non-root user (Issue #62)
* Switched to semantic versioning (see http://semver.org)
Mark BROKEN temporarily since ploy_ansible doesnt play nice with
Ansible >= 1.8 [1] and our sysutils/ansible port is at 1.8.3.
[1] https://github.com/ployground/bsdploy/issues/60
Reported by: dlangille
Update BSDploy and plugins to the latest, greatest, stable and gold 1.0.0
release while @tomlazar and @fschulze are running BSDploy training at
EuroPython 2014 :D
- Update RUN_DEPENDS to require >= 1.0.0 for all plugins
BSDploy is a comprehensive tool to provision, configure and maintain
FreeBSD jail hosts and jails.
Its main design goal is to lower the barrier to repeatable jail setups.
* Modular provisioning with plugins for VirtualBox, Amazon EC2 and
an achitecture to support more.
* Bootstrap complete jail hosts from scratch.
* Declarative configuration: All hosts and their properties defined
in ploy.conf are automatically exposed to Ansible.
* Imperative maintenance: Run Fabric scripts with ploy do JAILNAME
TASKNAME and have all of the hosts and their variables in fab.env.
* Configure ZFS pools and filesystems with whole-disk-encryption.
WWW: http://docs.bsdploy.net/
