Status of no_link: lib/libcrypto?

[h-vetinari]

This feedstock has had a no_link: directive since its inception:

openssl-feedstock/recipe/meta.yaml

Lines 14 to 15 in 7c460ed

	no_link: lib/libcrypto.so.1.0.0 # [linux]
	no_link: lib/libcrypto.1.0.0.dylib # [osx]

I'm pretty sure I messed this up in the 3.0 transition, because the new libcrypto library just has a SOVER of 3, and not 3.0.

Given that this most likely hasn't been used/functional for the last 2.5 years, I'm wondering if the original reason for adding it is still relevant?

@conda-forge/openssl

[jakirkham]

It doesn't look like it was discussed in staged-recipes either

xref: conda-forge/staged-recipes#553

Anaconda appears to still have it in their recipe

If I had to guess, OpenSSL relies on a certain layout. Adding no_link ensures that layout is met

Maybe someone else remembers more clearly