What is your problem/feature request?

Several recipes with a shared option in conancenter have to put tested recipe both in requirements and build requirements of test package, and it can break randomly with non-default shared flavor (usually shared=True) depending on availability of package with default shared value (usually shared=False).

Indeed, c3i builds for default shared option, and also the other flavor. But since c3i doesn't enforce shared option in build context (only in host context), test_package drags the default shared flavor in build requirements, and it may not be available yet while testing the non-default shared flavor in host context. So before running tests of a shared flavor, c3i should wait availability of package of build profile.

Another solution would be to enforce the same shared value in host & build context, but as you know (or you should know), it can become a nightmare on macOS due to SIP when there are executables linked to shared libs in build context and called at build time.

See also this comment #20089 (comment)

For example:

• libtool (libtool: less verbose package_info() #19501)
• protobuf (protobuf: improve discovery of protoc executable in build context #20089)
• grpc (grpc: use protobuf/<host_version> in build requirements + version range for zlib #19972)