lighttpd does not pull OpenSSL dependency
mad at madpilot.net
Fri Oct 28 10:05:04 UTC 2016
On 10/28/16 11:28, David Demelier wrote:
> 2016-10-27 18:35 GMT+02:00 Mathieu Arnold <mat at freebsd.org>:
>> Le 27/10/2016 à 17:00, Matthew D. Fuller a écrit :
>>> On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
>>> Mathieu Arnold, and lo! it spake thus:
>>>> Once you install openssl from ports, the ports framework will use
>>>> it, always.
>>> That is absolutely not the case since OpenSSL in base was updated to
>>> .so.8 and ports wasn't re-bumped past it. Everything gets confused
>>> all the time.
>> Well, that is another problem, and you are right, OpenSSL's shlib should
>> have been bumped, blame the former maintainer for that. I'll talk to the
>> new maintainer about that.
> What if we rename contrib libs that are used only in base?
> - /usr/lib/libfreebsd-(ssl|crypto)
> - /usr/lib/libfreebsd-kerberos* (don't know the name, I don't have
> access to a FreeBSD system ATM)
> And then, ports must always link to OpenSSL from ports or Kerberos,
> and so on that is in base but only for base tools.
That's what "making the library private" in base means.
Base already has some libraries in it which are "private", that means
not exposed to binaries outside of base for compiling or linking against.
Guido Falsi <mad at madpilot.net>
More information about the freebsd-ports