>       There might be a problem if any consumer used a full path for OpenSSL
>       binary /usr/sfw/bin/openssl or libraries so that's another situation
>       that will have to be checked with all consumers.

[ my apologies, one additional question ]

Besides the proposed symbolic link for /etc/sfw/openssl, does the
project plan to introduce any others such as one for
/usr/sfw/bin/openssl or other OpenSSL commands delivered under
/usr/sfw/bin?

dsc

Reply via email to