Date: Thu, 31 Aug 2023 19:14:13 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 266680] security/py-openssl: Update to 23.2.0 Message-ID: <bug-266680-21822-cP9zewakcu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266680-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-266680-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266680 --- Comment #22 from Charlie Li <vishwin@freebsd.org> --- (In reply to Li-Wen Hsu from comment #16) Anyone who sets legacy for the cryptography DEFAULT_VERSIONS is a consumer. While not visible on say FreshPorts or anything that tracks the default DEFAULT_VERSIONS, you still have to account for those cases. A separate PyOpenSSL-legacy port is not feasible or in users' best interest= in any case, since it would involve not only a new port, but possibly even an additional DEFAULT_VERSIONS knob. Such would only cause more confusion for users, who should not need to closely track cryptography and PyOpenSSL's development, to figure out which combination works with what. There is no A= PI compatibility guarantee between different versions of the two packages, and because the two packages do not sync development or releases between themselves, some contention in this area has and will continue to happen. H= ence why the best approach is to provide both 21.0.0 and whatever the current version is/becomes in the same port, gated on the DEFAULT_VERSIONS setting. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266680-21822-cP9zewakcu>