libgdal.so links against libcrypto, so the ebuild should depend on dev-libs/openssl or dev-libs/libressl. I've verified that gdal works with both libressl and openssl, but I haven't checked if it can be compiled when neither is present. My USE flags for gdal are "armadillo aux_xml curl geos gif hdf5 jpeg jpeg2k netcdf png postgres python spatialite sqlite threads", but due to the excessive build time, I haven't been able to check if libgdal always links against libcrypto, or if one of those USE flags triggers the linkage.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d6124f73611a87385edfaac2cc464a16afdf71b4 commit d6124f73611a87385edfaac2cc464a16afdf71b4 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-02-06 21:54:09 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-02-06 21:54:09 +0000 sci-libs/gdal: fix automagic dep on dev-libs/openssl Closes: https://bugs.gentoo.org/669302 Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Sam James <sam@gentoo.org> sci-libs/gdal/{gdal-3.2.1.ebuild => gdal-3.2.1-r1.ebuild} | 2 ++ 1 file changed, 2 insertions(+)
