ports/security/py-bcrypt, branch release/12.3.0

Remove # $FreeBSD$ from Makefiles.

2021-04-06T14:31:07Z

security/py-bcrypt: Update to 3.2.0

2021-01-16T12:18:31Z

Remove python 2.7 support from a few ports

2021-01-03T09:11:52Z

security/py-bcrypt: Fix runtime dependencies

2020-09-12T01:56:07Z

PR: 249235 Reported by: Andrew Fyfe MFH: 2020Q3 (blanket: runtime fix)

security/py-bcrypt: Update to 3.1.7

2019-06-22T14:46:10Z

security/py-bcrypt: Update to 3.1.6

2019-01-26T15:10:08Z

security/py-bcrypt: Update to 3.1.5

2018-12-13T23:08:40Z

Use PY_FLAVOR for dependencies.

2018-06-20T17:05:41Z

FLAVOR is the current port's flavor, it should not be used outside of this scope. Sponsored by: Absolight

Corrected shared library names that got the .abi3 suffix for python-36 and up after devel/py-cffi upgrade to 1.11.2

2018-01-05T20:02:03Z

This is the followup for the r457997 commit that updated devel/py-cffi to 1.11.2. As it turned out, the shared object names built by py-cffi has changed in python 36. Dependent ports can choose between installing such shared object as part of their plist, or generating them in the runtime and placing them into ~/.cache/{port-name}/ The former ones, that include the shared objects in their plist, got affected. 4 of the ports were failing explicitly in their py36 flavor during the strip phase. The other 6 were either missing strip entirely, or performed the strip operation without using explicit shared object names. These 6 ports didn't trigger any build errors, and were failing silently during the runtime, making the problem very hard to detect. Precisely, .abi3 suffix is now added for the py36 flavor of relevant ports. Here are the 10 ports that got affected and are now corrected: databases/py-psycopg2cffi devel/py-pygit2 devel/py-xattr devel/py-pyopencl devel/py-atomiclong multimedia/py-librtmp net/py-nnpy security/py-bcrypt security/py-cryptography security/py-pynacl All of them got the * in the stripped shared object name, and a PORTREVISION bump.

Convert Python ports to FLAVORS.

2017-11-30T15:50:30Z

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