On Sun, 20 Sep 2015 09:07:09 +0300 Andrew Savchenko <birc...@gentoo.org> wrote:
> Greetings, > > On Sat, 19 Sep 2015 23:04:14 +0200 hasufell wrote: > > Friends, > > > > I think it is time to import LibreSSL[0]. There are not many > > packages left that don't compile OOTB and those can be patched > > (e.g. dev-lang/ruby). > > > > My idea would be: > > > > 1. import "dev-libs/libressl" (this will block dev-libs/openssl) and > > introduce the global USE flag "libressl" with the following > > description: > > Please try to avoid such block, e.g. install libressl to a separate > location. This is easier to do when introducing package to the > tree, rather when facing large-scale blockers. Otherwise one day we > will face nasty bug like mutual heimdal/mit-krb5 blocker[1], where > foo will work only openssl, bar only with libressl and users will > need both. If they're abi incompatible but share some namespace (symbols, soname, library names, etc.) I think that's a terrible idea since that'd introduce runtime bugs. I've faced something like that recently: opencv can link to qt4 or qt5. but if you link a qt5 program to opencv[qt4] it'll fail in terrible ways. you'd have the same replacing qt4/qt5 by libressl/openssl.
