The cryptsetup/cryptsetup-2.1.0 ebuild is broken. Specyfic code: " LIB_DEPEND=" dev-libs/json-c:=[static-libs(+)] dev-libs/libgpg-error[static-libs(+)] dev-libs/popt[static-libs(+)] >=sys-apps/util-linux-2.31-r1[static-libs(+)] argon2? ( app-crypt/argon2:=[static-libs(+)] ) gcrypt? ( dev-libs/libgcrypt:0=[static-libs(+)] ) nettle? ( >=dev-libs/nettle-2.4[static-libs(+)] ) openssl? ( !libressl? ( dev-libs/openssl:0=[static-libs(+)] ) libressl? ( dev-libs/libressl:0=[static-libs(+)] ) ) pwquality? ( dev-libs/libpwquality[static-libs(+)] ) sys-fs/lvm2[static-libs(+)] udev? ( virtual/libudev[static-libs(+)] )" " Here we can see that we have to enable openssl to enable libressl. LibreSSL is an drop in replacenet for OpenSSL and only one USE flag for each should be selected at a time.
Enable USE=openssl for openssl-like functionality, then -libressl or +libressl to select between dev-libs/openssl & dev-libs/libressl. This is similar to the ffmpeg/libav situation. Enable USE=ffmpeg for ffmpeg-like functionality, then -libav or +libav to select between media-libs/ffmpeg & media-libs/libav. I'm pretty sure this is by design & intent, not a bug.
(In reply to Ben Kohler from comment #1) > Enable USE=openssl for openssl-like functionality, then -libressl or > +libressl to select between dev-libs/openssl & dev-libs/libressl. > > This is similar to the ffmpeg/libav situation. Enable USE=ffmpeg for > ffmpeg-like functionality, then -libav or +libav to select between > media-libs/ffmpeg & media-libs/libav. > > I'm pretty sure this is by design & intent, not a bug. it's really misleading, tho
Please read this: https://wiki.gentoo.org/wiki/Project:LibreSSL
Right, that page reinforces what I'm saying. Look at the 5th CODE block and the paragraph immediately after it.
I propose we just change "openssl" USE flag to "ssl", to avoid misunderstandings (and maake it simpler)
But it's not the only ssl provider, there is also gnutls which is optional. This openssl flag enables support for openssl or the openssl-fork-now-called-libressl. I don't think there is anything to be fixed here except getting used to the scheme like we have done for libav.
(In reply to Ben Kohler from comment #6) > But it's not the only ssl provider, there is also gnutls which is optional. > This openssl flag enables support for openssl or the > openssl-fork-now-called-libressl. > > I don't think there is anything to be fixed here except getting used to the > scheme like we have done for libav. but it's not in the ebuild, is it?
(In reply to Ben Kohler from comment #1) > Enable USE=openssl for openssl-like functionality, then -libressl or > +libressl to select between dev-libs/openssl & dev-libs/libressl. > > This is similar to the ffmpeg/libav situation. Enable USE=ffmpeg for > ffmpeg-like functionality, then -libav or +libav to select between > media-libs/ffmpeg & media-libs/libav. > > I'm pretty sure this is by design & intent, not a bug. closing the bug seems like "fmmpeg vs libav" is the way to do it
