Here are my notes on the users of the openssl-1.0 package: > File: networking.scm
pidentd: Does not build with current OpenSSL, no newer releases or development No dependents vde2: Does not build with current OpenSSL. Dependency changed to WolfSSL (unpackaged): https://github.com/virtualsquare/vde-2/issues/2 Depended on by QEMU but not qemu-minimal (optional): > File: web.scm cadaver: Does not build with current OpenSSL Last release in 2009 No dependents > File: web-browsers.scm dillo: Does not build with current OpenSSL Status? https://www.dillo.org/Plans.html No dependents > File: android.scm adb: Does not build with current OpenSSL Surely there is a new version of adb that supports the current OpenSSL. Depended on by fastboot > File: crypto.scm eschalot: Does not build with current OpenSSL, no newer releases or development No dependents > File: messaging.scm psyclpc: Does not build with current OpenSSL No dependents > File: ntp.scm tlsdate: Does not build with current OpenSSL. Forked by ChromiumOS as the project is abandoned: https://github.com/ioerror/tlsdate/issues/199 No dependents > File: rust.scm > File: crates-io.scm For the Rust bootstrap, we can keep openssl-1.0 as a hidden-package. Help wanted dealing with the crates that depend on openssl-1.0.
