[question] Revisions with different dependencies in requires

I have a question about how revisions are supposed to work with packages that can produce multiple binaries depending on different requires. For example, we need to build opencv with cuda 10 and 11. Without revisions, the workflow is

• Create conanfile.py with opencv with requires = 'cuda/10.0'
• buid -> export pkg
• edit conanfile.py and update requires = 'cuda/11.0'
• build -> export pkg
• if I want to use opencv binary with cuda 11, from the consuming library, I just needs to specify requires = ('opencv/4.5.3','cuda/11.0'). Same for cuda 10.

However, with revisions enabled, this workflow no longer works because once I edited the conanfile.py, it fixes the revision. From the client, I can no longer have a simple requires = ('opencv/4.5.3','cuda/11.0'). I must now have requires = ('opencv/4.5.3#RREF','cuda/11.0'), if the latest revision is not cuda 11.0. What is the way to avoid having explicit RREF yet still be able to choose different cuda versions?

• I’ve read the CONTRIBUTING guide.

[memsharded]

This will possible go together with https://github.com/conan-io/conan/pull/10046, we will investigate if using lockfiles is a better solution than --require-override arg, which might not be the best UI

[memsharded]

This will finally be implemented using lockfiles. Added by https://github.com/conan-io/conan/pull/10713, will be released in next 2.0-alpha.6