Date: Thu, 9 Apr 2015 15:05:22 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-ports@freebsd.org, Bryan Drewery <bdrewery@FreeBSD.org> Subject: Re: LibreSSL infects ports, causes problems Message-ID: <20150409130521.GQ95321@ivaldir.etoilebsd.net> In-Reply-To: <20150409115942.GA81282@lorvorc.mips.inka.de> References: <slrnmib1ur.2jau.naddy@lorvorc.mips.inka.de> <5525E609.70402@FreeBSD.org> <20150409115942.GA81282@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--xYeFQzU4VZLrHqxU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 09, 2015 at 01:59:42PM +0200, Christian Weisgerber wrote: > Bryan Drewery: >=20 > > Are you mixing ports and packages? >=20 > No. Ports only. >=20 Some how you have mixed up things between base openssl and libressl, when starting to activate libressl if you are using ports only you have to be ex= tra careful, (same goes with ncurses or ports openssl) just installing those po= rts is enough to "pollute" nearly anything you build after with a dependency on= it (well anything that does link to libssl, libcrypto) If it very complicated = and error prone to cherry pick "only take base openssl here, only ports openssl there" the only "safe" way to solve this situation and being consistent is = to always skip the version from base and enforce the version for ports. (the otherway around is impossible - very complicated) That is the price of building in place... Regards, Bapt --xYeFQzU4VZLrHqxU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUmeREACgkQ8kTtMUmk6EwL4QCgkxRbRaC146BZAFTHH7aCRHPH IxcAoMI31mtSzFwwVLkYCIJUK5RZZiv+ =/yZ5 -----END PGP SIGNATURE----- --xYeFQzU4VZLrHqxU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150409130521.GQ95321>