Comment 2 for bug 1953708

The current discussion in the cl+ssl issue 144 is about taking the library from alternative package managers, I am not sure will pkg-config be suitable for that or not.

Anyways, even if cl+ssl was able to find good OpenSSL automatically, it's necessary to have possibility for user to to override the OpenSSL path with his own value. The question with evaluated parameter remains.

The cffi-c-library ASDF component looks interesting, is it a part of mainstream CFFI or some experimental code? The foreign lib path it detects via pkg-config, is it frozen at build time, or determined dynamically during the program execution? I am also interested, because I was thinking of a similar, but simpler component type - simply declare that a system has foreign dependency, which would allow to collect a list of foreign dependencies for an application, maybe print some help about their installations.