Date: Wed, 5 May 2021 21:08:26 +0200 From: Michael Gmelin <freebsd@grem.de> To: Stefan Esser <se@freebsd.org>, 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: <881013A8-7223-4A35-8FBE-5247889D2D72@grem.de> In-Reply-To: <12e142be-43c8-70fc-d0d8-d17969d8c734@freebsd.org> References: <12e142be-43c8-70fc-d0d8-d17969d8c734@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5. May 2021, at 18:56, Stefan Esser <se@freebsd.org> wrote:
>=20
> =EF=BB=BFAm 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).
Stefan=E2=80=98s suggestion is AFAIK the best we can do.
mail/opensmtpd has an example of that, but it still requires the user to act=
ively select the OpenSSL library (mixing OpenSSL libraries in a package set i=
s problematic).
Best,
Michael
>=20
> You can mark the port as broken if the user has selected "base" and
> this is incompatible with the port's requirements. E.g.:
>=20
> .include <bsd.port.pre.mk>
>=20
> .if ${SSL_DEFAULT} =3D=3D base
> BROKEN_FreeBSD_11=3D OpenSSL 1.1 required
> .endif
>=20
> .include <bsd.port.post.mk>
>=20
> 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.
>=20
>> 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 fo=
r
>> similar way about ssl setting.
>=20
> 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.
>=20
> 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).
>=20
> Regards, STefan
>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?881013A8-7223-4A35-8FBE-5247889D2D72>