Moving libcrypto.so.* back to /lib

[Chris Adams]

Once upon a time, Richard W.M. Jones <rjones at redhat.com> said:
> libguestfs builds its appliance on the fly by concatenating together
> files [library files, binaries and data files] from the host.  We
> express this requirement by mapping the location of those files into
> dependencies.

Why can't it just depend on libcrypto.so.<vesion>, and then use the
linker to find the libraries at run-time?  Depending on fixed paths
seems like a bad idea.
-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.