You wrote a cool network client or server. It encrypts connections
using TLS. Your test suite needs to make TLS connections to itself.
Uh oh. Your test suite probably doesn't have a valid TLS certificate.
Now what?
trustme is a tiny Python package that does one thing: it gives you
a fake certificate authority (CA) that you can use to generate fake
TLS certs to use in your tests. Well, technically they're real
certs, they're just signed by your CA, which nobody trusts. But you
can trust it. Trust me.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-trustme listed in the above command, you can pick from the names under the Packages section.
*: Replace USES=pycryptography* with USE_PYTHON=cryptography{,_build,_test}
- Introduce USE_PYTHON=cryptography{,_build,_test}
- Switch all 96 ports from USES=pycryptography to with
USE_PYTHON=cryptography{,_build,_test}
- Remove Mk/Uses/pycryptography.mk
PR: 273727
Approved by: tcberner (portmgr)
Exp-run by: antoine
framework: convert tree to use USES=pycryptography
A future commit will update to security/py-cryptography will introduce a
rust dependency.
PR: 254853
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Follow up on devel/py-futures port removal in r559976
The devel/py-futures port was removed in r559976 as it was for
Python 2.7 only and no longer referenced in the default cases.
However it was still defined in Mk/Uses/python.mk in PY_FUTURES,
leaving a dangling reference.
Remove it from Mk/Uses/python.mk and from affected ports, as
it was already an empty definition for Python 3.6+
Bump minimal Python version of security/theonionbox to 3.6+
You wrote a cool network client or server. It encrypts connections
using TLS. Your test suite needs to make TLS connections to itself.
Uh oh. Your test suite probably doesn't have a valid TLS certificate.
Now what?
trustme is a tiny Python package that does one thing: it gives you
a fake certificate authority (CA) that you can use to generate fake
TLS certs to use in your tests. Well, technically they're real
certs, they're just signed by your CA, which nobody trusts. But you
can trust it. Trust me.
WWW: https://github.com/python-trio/trustme
