Date: Wed, 22 May 2019 16:48:31 -0400 From: Charlie Li <ml+freebsd@vishwin.info> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Bernard Spil <brnrd@freebsd.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r502278 - head/security/libressl-devel Message-ID: <657177bf-38f7-c5f6-0d83-e6d47c2445e7@vishwin.info> In-Reply-To: <20190522194458.GA71248@FreeBSD.org> References: <201905221846.x4MIkh29013093@repo.freebsd.org> <20190522194458.GA71248@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HCEFPwqPxDCnoAtPxCRAvHFztZvcIZAld Content-Type: multipart/mixed; boundary="mBO3JUZrqOtKrjOdijFQoh79D8EgsWQ4z"; protected-headers="v1" From: Charlie Li <ml+freebsd@vishwin.info> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Bernard Spil <brnrd@freebsd.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Message-ID: <657177bf-38f7-c5f6-0d83-e6d47c2445e7@vishwin.info> Subject: Re: svn commit: r502278 - head/security/libressl-devel References: <201905221846.x4MIkh29013093@repo.freebsd.org> <20190522194458.GA71248@FreeBSD.org> In-Reply-To: <20190522194458.GA71248@FreeBSD.org> --mBO3JUZrqOtKrjOdijFQoh79D8EgsWQ4z Content-Type: text/plain; charset=utf-8 Content-Language: en-GB-large Content-Transfer-Encoding: quoted-printable Alexey Dokuchaev wrote: > On Wed, May 22, 2019 at 06:46:43PM +0000, Bernard Spil wrote: >> New Revision: 502278 >> URL: https://svnweb.freebsd.org/changeset/ports/502278 >> >> Log: >> security/libressl-devel: Update to 2.9.2 >=20 > So what's the difference with non-devel port then? >=20 -devel currently has an option to "enable" TLS 1.3 support, which for the 2.9 series remains some empty functions and defines. Python itself, among other ports that check for and use the SSL library's TLS 1.3 capabilities, will not build with the option enabled, however, because their configure process checks exactly those functions and defines. Otherwise, when upstream's latest branch is considered stable, our -devel and not ports are at the same version, not least so that those of us with libressl-devel in DEFAULT_VERSIONS don't have to keep changing back and forth and rebuilding every port with USES=3Dssl every time. When= upstream releases a new branch, it is almost always marked not stable in their release notes until a .1 or .2 release; this is when -devel and non-devel have differing versions. --=20 Charlie Li =E2=80=A6nope, still don't have an exit line. (This email address is for mailing list use; replace local-part with vishwin for off-list communication if possible) --mBO3JUZrqOtKrjOdijFQoh79D8EgsWQ4z-- --HCEFPwqPxDCnoAtPxCRAvHFztZvcIZAld Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE/3/Cqr5a+41PbEb+jnB43vIDq2wFAlzltaAACgkQjnB43vID q2w2aQ/+NJotZNc+2ih6lqTAmePnUfWFxvRBBRm2o1RML4B9ULlC1ZeL09Xr5svk kADKX9ETQQ3yYEBQgIZ1Bzv8rL+Zh8Z3CyGTnJTcvX1JolX6+NZVBJcetpYxRRWJ oledUDWfgxNSPJEUTxkFgjoUpmVAq7WZzf1K5uV9LjKO246j14L/sA2Yswrcrt+e 2JzrZcB4oePbYQUxWRUgCIrhDKdoxin5kZ8yPlXFpM1Uo6o9b165/q2iGi5Ohavu 9VZ9Fy8qkioodVs8SLRMeeMkEpd2lHhTD2JN4cPst9hf8i6eS2mNhE+YmRdFL6N6 S05wCzDK7st/pWAZWxEILXghv3tdtPdC+6aXPuKO+pIeVBdo8CRMlvuoJqQhY7RX +ncnjGj2Aw+ggGmzf28XxOaBjvy2xmnh0bCgwyXTTI8OAZ15mwIXJ760CM1VjALG WkqZgWuARHqsEtf53NICH56C1fmuPIAtA2ChqRMB/bDMQFXeQSdD6nWy0pxKUzzA 6gMa00923s5fHaJacdk09d3VWn3CQCVqDdzV2gkXcP6sbMNPPDzJ9bW4GQRtQlGY Z6oXiQquKGS9UxSonJ1MPvQEzvfS331YUWxwMuDUSFpcGcRUA95YtyI6KCT6FQ9z qQKhr+MpkghpEb4qibCVgpC2tHYbs9ueIKv0Aif8sNrNMyFxPsI= =1eOu -----END PGP SIGNATURE----- --HCEFPwqPxDCnoAtPxCRAvHFztZvcIZAld--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?657177bf-38f7-c5f6-0d83-e6d47c2445e7>