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
- Switch from deprecated USES=twisted:run to py-twisted, py-txamqp
already depends on py-twisted
- Remove dependency on the python2 symlink
Reported by: pkg-fallout
With hat: portmgr
The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.
PR: 214780
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
This may be useful to balance load between CPU cores or to
listen on IPv6 [::] in addition to IPv4 *.
PR: 198734
Submitted by: Gennady Karpov <gekar@yandex-team.ru>
Approved by: maintainer
- Fix with newer Django [2]
- Lots of other cleanups and improvements, including moving the data to a more
standard location
- Take maintainership, maintainer has not responded to PRs in many months
PR: ports/181043 [1]
PR: ports/185097 [2]
Submitted by: brd [1]
Submitted by: swills (myself) [2]
Approved by: maintainer timeout (bsdports@wayfair.com, >3 months)
twisted can be configured with the arguments run or build to replace
the previous USE_TWISTED_RUN and USE_TWISTED_BUILD knobs. The twisted
components can be added as comma-separated arguments. If you previously
wrote
USE_TWISTED= yes
USE_TWISTED= conch names
USE_TWISTED_RUN= yes
you now would write
USES= twisted
USES= twisted:conch,names
USES= twisted:run
- fix comments in carbon's rc-script
- checksum change, that was in original PR is rejected, because it fetches
fine with old checksums and fails to fetch with new ones.
while here:
- change etc/carbon to %%ETCDIR%% in pkg-plist
- remove unneeded newlines in files/pkg_message.in
- add license (AL2)
- remove BUILD_DEPENDS (setup.py didn't cheking for it on build phase)
- limit python version to 2.x
- tab -> space in pkg-descr:WWW
- this port depends on twisted both directly and via USE_TWISTED. Since
I wasn't able to find which twisted components it actually needed, I
just dropped USE_TWISTED and let the port to depend on it via
devel/py-twisted meta-port
PR: 170920
Submitted by: Chris McCoy <bsdports at wayfair dot com> (maintainer)
