mupdf should not depend on openssl if openssl USE is not set.
True, thanks for spotting it. I'll fix this in the next bump.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5247eb5569e7573eba63db4cf5e6012607e1a6d commit a5247eb5569e7573eba63db4cf5e6012607e1a6d Author: Virgil Dupras <vdupras@gentoo.org> AuthorDate: 2019-02-19 20:22:34 +0000 Commit: Virgil Dupras <vdupras@gentoo.org> CommitDate: 2019-02-19 21:01:02 +0000 app-text/mupdf: fix libressl and openssl openssl's requirements is actually 1.1+. prior to this change, mupdf compiled with openssl support unless openssl 1.1+ was installed. libressl support requires a patch to work properly. Also, other minor fixes. See closed bugs. Closes: https://bugs.gentoo.org/671062 Closes: https://bugs.gentoo.org/623732 Closes: https://bugs.gentoo.org/669698 Closes: https://bugs.gentoo.org/670832 Signed-off-by: Virgil Dupras <vdupras@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 app-text/mupdf/files/mupdf-1.14-libressl.patch | 45 +++++++ .../files/mupdf-1.14-r3-openssl-curl-x11.patch | 35 ++++++ app-text/mupdf/mupdf-1.14.0-r3.ebuild | 132 +++++++++++++++++++++ 3 files changed, 212 insertions(+)