| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=455210
|
|
|
As far as I (the author) knows, sshuttle is the only program that solves
the following common case:
* Your client machine (or router) is Linux, FreeBSD, or MacOS.
* You have access to a remote network via ssh.
* You don't necessarily have admin access on the remote network.
* The remote network has no VPN, or only stupid/complex VPN protocols
(IPsec, PPTP, etc). Or maybe you are the admin and you just got
frustrated with the awful state of VPN tools.
* You don't want to create an ssh port forward for every single host/port
on the remote network.
* You hate openssh's port forwarding because it's randomly slow and/or
stupid.
* You can't use openssh's PermitTunnel feature because it's disabled by
default on openssh servers; plus it does TCP-over-TCP, which has
terrible performance
WWW: https://github.com/sshuttle/sshuttle
While I'm here, patch out pytest-runner from setup_requires and add it
to tests_require. It's a test dependency, and pytest upstream
shouldn't 'recommend' otherwise in its 'Usage:' docs.
[1] https://github.com/sshuttle/sshuttle/issues/115
Requested by: John Kozubik (rsync.net, Inc) via freebsd-jobs
Notes:
svn path=/head/; revision=423637
|
