Date: Sun, 25 Nov 2018 18:51:33 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Mathieu Arnold <mat@FreeBSD.org> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org>, portmgr@freebsd.org Subject: Re: ssl=base Message-ID: <b599559b-8c82-523d-fece-348d1cf4e22e@grosbein.net> In-Reply-To: <20181125114601.b56stbs5nr64mhkv@atuin.in.mat.cc> References: <6a506622-f08b-3e52-52c4-3eb63147c328@grosbein.net> <20181125114601.b56stbs5nr64mhkv@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
25.11.2018 18:46, Mathieu Arnold wrote:
>> As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
>> prevents building this port using FreeBSD 12 and base system libssl
>> when libressl is installed?
>>
>> While building with ssl=base, the port itself does not include headers
>> from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search path for linking stage.
>>
>> I see no way to override noted (wrong) check-depends restriction, and that's not good.
>
> Because you either use OpenSSL from the base system, or you install an
> *SSL variant from ports and use it. You cannot mix half of the stuff
> from the base system and half of the stuff from a port version of *SSL.
Why can't you use LibreSSL port for some ports and base libssl for other ports?
That is, net/mpd5 links with base system libfetch that depends on base libssl,
so it is example of port that cannot be built with LibreSSL.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b599559b-8c82-523d-fece-348d1cf4e22e>