possibility to require itself, previous version visible=False

[memsharded]

Changelog: Feature: Allow a recipe to requires(..., visible=False) a previous version of itself without raising a loop error
Docs: https://github.com/conan-io/docs/pull/XXXX

[gegles]

@memsharded, any progress/update on this? Just curious. Thx!

[memsharded]

@gegles we are still consider this, the possible risks and future challenges.

What is your use case? Could you please elaborate why are you interested in this feature? So far we have considered it for a very extraordinary situation with openssl, but I can't think of many other cases beyond it.

[gegles]

@gegles we are still consider this, the possible risks and future challenges.

What is your use case? Could you please elaborate why are you interested in this feature? So far we have considered it for a very extraordinary situation with openssl, but I can't think of many other cases beyond it.

Yes, the use case I am interested in is the OpenSSL/FIPS use case that started this whole thing. See the initial idea presented by @jcar87 here.

You're right, as of now, I don't see any other use case for this... but , from my POV, this would be the most elegant and useful way for the community to get the exact right set of binaries directly within the single openssl recipe/package and without needing to do any weird repackaging outside...

As long as it does not harm anything else, I believe loosening the restrictions just enough for something like this to be possible would be a great thing.

Thanks!