diff options
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 30 |
1 files changed, 30 insertions, 0 deletions
@@ -13,6 +13,36 @@ All ports committers are allowed to commit to this file. 20171130: AUTHOR: mat@FreeBSD.org + 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 the port is + using distutils but flavors are not wanted. + + A new USE_PYTHON=optsuffix that will adds 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 it will only generate flavors for the versions in PYTHON2_DEFAULT + and PYTHON3_DEFAULT. Define BUILD_ALL_PYTHON_FLAVORS in your make.conf to + generate all possible flavors. A port can set USE_PYTHON=allflavors to have + all the flavors and not simply the default ones. + + 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} + +20171130: +AUTHOR: mat@FreeBSD.org + To help with flavored ports, helpers are available. In these, replace <*> with the flavor name. |