tink-cc + Bazel with OpenSSL 3

[VirtualTim]

Hi, I'm currently in the process of adding tink-cc as a bazel dependency. I'm essentially following this guide: https://developers.google.com/tink/setup/cc#installation.
However I have a small issue; the MODULE.bazel uses boringssl, but my application is already using OpenSSL 3, and the two can't be mixed.

tink-cc/MODULE.bazel

Lines 50 to 53 in 25ac091

	bazel_dep(
	name = "boringssl",
	version = "0.20251002.0",
	)

tink-cc supports OpenSSL 3, so I'm patching the MODULE.bazel using archive_override. But that feels a bit hacky/fragile. Is there a better way, or something tink-cc could do to make workflow better?

[tholenst]

I don't have anything useful to say at the moment, but just want to link the related bazelbuild/bazel#26827

[tholenst]

Another data point: https://issues.chromium.org/issues/42220000

Our plan is likely to finish the symbol prefixing in https://issues.chromium.org/issues/42220000 and then get rid of the OpenSSL support in Tink (but allowing Tink and OpenSSL to be in the same binary). However, this isn't really decided yet, and if you have input about this plan then please add it here.

[VirtualTim]

I was hoping this was more "solved" in Bazel. This sort of issue isn't specific to BoringSSL, but also affects think like zlib/zlib-ng.