Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 May 2021 18:55:47 +0200
From:      Stefan Esser <se@freebsd.org>
To:        Yasuhiro Kimura <yasu@utahime.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Message-ID:  <12e142be-43c8-70fc-d0d8-d17969d8c734@freebsd.org>
In-Reply-To: <20210506.010002.255215505975340477.yasu@utahime.org>
References:  <8151EFB0-635D-4648-AF0B-653E45584F1A@grem.de> <20210505.232208.1752175478734160028.yasu@utahime.org> <20210505173202.36f1c307@bsd64.grem.de> <20210506.010002.255215505975340477.yasu@utahime.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6veyCbbFAYxDX81kkUrpLjqPkg3NDjsZ1
Content-Type: multipart/mixed; boundary="wns8g9NQqp4rBXlrIsFJjkj5EbnN7zJ63";
 protected-headers="v1"
From: Stefan Esser <se@freebsd.org>
To: Yasuhiro Kimura <yasu@utahime.org>
Cc: freebsd-ports@freebsd.org
Message-ID: <12e142be-43c8-70fc-d0d8-d17969d8c734@freebsd.org>
Subject: Re: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
References: <8151EFB0-635D-4648-AF0B-653E45584F1A@grem.de>
 <20210505.232208.1752175478734160028.yasu@utahime.org>
 <20210505173202.36f1c307@bsd64.grem.de>
 <20210506.010002.255215505975340477.yasu@utahime.org>
In-Reply-To: <20210506.010002.255215505975340477.yasu@utahime.org>

--wns8g9NQqp4rBXlrIsFJjkj5EbnN7zJ63
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Am 05.05.21 um 18:00 schrieb Yasuhiro Kimura:
> You misunderstand my intention. What I would like to do is to make a
> port use security/openssl instead of base OpenSSL even if user sets
> 'DEFAULT_VERSIONS+=3Dssl=3Dbase' in /etc/make.conf (or user doesn't
> customize setting about ssl at all).

You can mark the port as broken if the user has selected "base" and
this is incompatible with the port's requirements. E.g.:

=2Einclude <bsd.port.pre.mk>

=2Eif ${SSL_DEFAULT} =3D=3D base
BROKEN_FreeBSD_11=3D      OpenSSL 1.1 required
=2Eendif

=2Einclude <bsd.port.post.mk>

You can of course add a better message, and the user can decide to
try the compilation again after changing the default. But this will
of course prevent the building of official packages for FreeBSD-11.

> As I wrote previous mail, if 'USES=3Dpython:3.8+' is specified in
> Makefile of a port, lang/python38 is used for the port event if user
> adds 'DEFAULT_VERSIONS+=3Dpython=3D3.7' in /etc/make.conf. I'm looking =
for
> similar way about ssl setting.

You could add a dependency on the openssl port and make sure, that
the port's include file and library is used in preference of the
base version on FreeBSD-11.

But you have to consider the risk of mixing references to the base and
the ports version in one binary (e.g. other libraries are linked in that
had been built against the base version).

Regards, STefan


--wns8g9NQqp4rBXlrIsFJjkj5EbnN7zJ63--

--6veyCbbFAYxDX81kkUrpLjqPkg3NDjsZ1
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmCSzhQFAwAAAAAACgkQR+u171r99UQO
qAgAmMc8KgKnXMTMm3J5u0yP6BBVP3QUyZcWIp6UAepm5kF9AHvIx3vIY9WJNoCpjWLFHgEXOIIl
wrE2MW6YJkhvfO4vekzgCLwQt7NQV736ycDty4/0eA12WNkFHeXB+HBoZxNxNCjgDB6oN0pIhmqY
PoVrhJq/1AWbZAwYcPtpgJCnRpD2uSDbr31o5jhQj8v85yPsGiiU6lav4YCP/HDfKKSV+nUdmskD
SZjtiwdirmYqroMgtvUff/XogHv5YLPNiQvMDHKaqXKEyxVubvxLxqPFl5P/esRXCVW2stG8Jvyf
gjR/bvv9tD2SiCFRT2D8lqO6AGE8dR/WOvbOh3qO3w==
=aWud
-----END PGP SIGNATURE-----

--6veyCbbFAYxDX81kkUrpLjqPkg3NDjsZ1--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12e142be-43c8-70fc-d0d8-d17969d8c734>