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
Changed RUN_DEPENDS from devel/py-lockfile to devel/py-fasteners:
Fixed bug #1320641 and others regarding lockfile
- swap from lockfile to fasteners module
- use an fcntl() style lock for process lock of duplicity cache
- lockfile will now clear if duplicity is killed or crashes
See the changelog file for more information.
Changes: http://www.nongnu.org/duplicity/CHANGELOG
Approved by: garga (mentor)
Differential Revision: https://reviews.freebsd.org/D11548
This is ABI-compatible with 1.0.0, but due to an accident
upstream with releasing 1.0.1 with a reversed shlib version,
they released 2.0.0 with only a restoration of the shlib
version of 2.
Submitted by: Danilo G. Baio (dbaio) <dbaio@bsd.com.br>
- Modify options descriptions to match currents standards
- Fix PEXPECT option, misc/py-pexpect does not install
pexpect executable, convert check to path independent one
- Convert to options helpers, break lines around 80 characters
- Regenerate patch with make makepatch
PR: 213145 [1]
Submitted by: Arnaud de Prelle [1]
Changes: http://duplicity.nongnu.org/CHANGELOG
- Fixed bug #1570293 duplicity is very slow due to excessive fsync
- LIB_DEPENDS from librsync to librsync1
PR: 210073
Submitted by: Philip Jocks <freebsdbugs@filis.org>
Approved by: jase (maintainer timeout)
- CloudFiles backend is updated to support (and use by default)
Rackspace's all-encompassing Python API library pyrax. As the
library is not currently in the Ports Collection, revert the
default module used for the backend to py-cloudfiles. This can
be overridden by using --cf-backend=pyrax at runtime
- Pet portlint(8), rename Makefile variable file to f
- Update pkg-message to mention mega backend
- Change to PYDISTUTILS_AUTOPLIST=YES, list documentation in
PORTDOCS and remove pkg-plist
Changes: http://duplicity.nongnu.org/Changelog.GNU
Duplicity itself is not fully Python 3 compatible - there's multiple
instances of "print" as command and all the unicode vs bytes string
handling needs fixing to allow working unicode filename support.
Python 3 support is currently planned for the 0.7 branch.
- Add options for GIO and Ubuntu One backends as their dependancies
are now available in the Ports Collection
Changes: http://duplicity.nongnu.org/CHANGELOG
Too many changes since 0.6.13 to list, see:
1. /usr/local/share/doc/duplicity/CHANGELOG, or
2. http://www.nongnu.org/duplicity/CHANGELOG
For the port, the version upgrade and maintainer change are from the PR.
Thanks to the former maintainer for his past hard work, and confirming
the change.
Additionally, add some cleanups of my own:
1. More accurate comment
2. Make NLS an OPTION
3. Minor simplification to the Makefile logic
PR: ports/162507
Submitted by: Jase Thew <freebsd@beardz.net>
Feature safe: yes
