Date: Thu, 6 May 2021 12:46:14 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Dima Panov <fluffy@FreeBSD.org>, Chris <portmaster@bsdforge.com>, 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: <ca940e57-bf71-e8e9-caa2-98a1daa43d57@grosbein.net> In-Reply-To: <a4da2161-1d84-4dae-8be3-ae99305b6150@Canary> References: <8151EFB0-635D-4648-AF0B-653E45584F1A@grem.de> <20210505.232208.1752175478734160028.yasu@utahime.org> <eb646c67dea5797baa51c22b54e50568@bsdforge.com> <20210506.011037.2056308540818173996.yasu@utahime.org> <154fe2a4cccad0fb69ef5215fe265456@bsdforge.com> <a4da2161-1d84-4dae-8be3-ae99305b6150@Canary>
next in thread | previous in thread | raw e-mail | index | archive | help
06.05.2021 10:49, Dima Panov wrote: > Chris, your suggestion leads to dll hell due to mix-links between ssl libraries :( > At least, your setup easily face up situation where one lib will be built with “port openss” and consumers still get a “base openssl”. > DEFAULT_VERSION here is set to avoid a such situation — the whole ports collection should be linked with ONE ssl/crypto library. I disagree. There is no reason for "leaf" ports to depend on ports version of openssl and this is impossible in come cases. For example, net/mpd5 port that links with base libfetch that links with base openssl. So, net/mpd5 must NOT be linked with ports openssl and frankly, it needs not. Global inflexible knob for whole ports tree is bad thing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ca940e57-bf71-e8e9-caa2-98a1daa43d57>