Changeset View
Changeset View
Standalone View
Standalone View
head/CHANGES
Updating Information for FreeBSD ports developers | Updating Information for FreeBSD ports developers | ||||
This file is maintained by portmgr@FreeBSD.org and copyrighted by the | This file is maintained by portmgr@FreeBSD.org and copyrighted by the | ||||
FreeBSD Foundation. | FreeBSD Foundation. | ||||
This file contains major changes to ports and the ports infrastructure. | This file contains major changes to ports and the ports infrastructure. | ||||
Intended audience are ports committers, maintainers and other | Intended audience are ports committers, maintainers and other | ||||
developers. User oriented changes should be submitted for inclusion | developers. User oriented changes should be submitted for inclusion | ||||
in the release notes and/or placed into UPDATING. | in the release notes and/or placed into UPDATING. | ||||
All ports committers are allowed to commit to this file. | All ports committers are allowed to commit to this file. | ||||
20171130: | 20171130: | ||||
AUTHOR: mat@FreeBSD.org | 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 <*> | To help with flavored ports, helpers are available. In these, replace <*> | ||||
with the flavor name. | with the flavor name. | ||||
*_PKGNAMEPREFIX *_PKGNAMESUFFIX *_PLIST *_DESCR will overwrite the variable. | *_PKGNAMEPREFIX *_PKGNAMESUFFIX *_PLIST *_DESCR will overwrite the variable. | ||||
*_CONFLICTS *_CONFLICTS_BUILD *_CONFLICTS_INSTALL *_PKG_DEPENDS | *_CONFLICTS *_CONFLICTS_BUILD *_CONFLICTS_INSTALL *_PKG_DEPENDS | ||||
*_EXTRACT_DEPENDS *_PATCH_DEPENDS *_FETCH_DEPENDS *_BUILD_DEPENDS | *_EXTRACT_DEPENDS *_PATCH_DEPENDS *_FETCH_DEPENDS *_BUILD_DEPENDS | ||||
*_LIB_DEPENDS *_RUN_DEPENDS *_TEST_DEPENDS will append to the variable. | *_LIB_DEPENDS *_RUN_DEPENDS *_TEST_DEPENDS will append to the variable. | ||||
▲ Show 20 Lines • Show All 3,410 Lines • Show Last 20 Lines |