[question] Keying packages on libstdc++ version? Autodetecting it?

[nextsilicon-itay-bookstein]

What is your question?

Hi! I'm trying to push packages to a conan artifactory instance and reuse them in compatible environments. To that end I added keying for the packages through settings_user.yml. Specifically, I added keying on (distro, distro_version). However I found that's not enough since we have easybuild-based environments which provide libstdc++ versions that are newer than the distro's, and then packages produced in that environment cannot be used on the vanilla distro itself because they demand newer symbols from libstdc++.

I thought I might further key the package on a compiler.libcxx.version setting field I would add, and was wondering if that makes sense and what's the best practice here.

I was also wondering if I could somehow extend the APIs available at profile templating time in order to be able to call some code to autodetect this property, instead of doing it outside and passing it in via an environment variable. WDYT?

Lastly, I was wondering if more things (like the distro module and maybe also subprocess) could be made available during template formatting to make this keying easier?

Have you read the CONTRIBUTING guide?

• [X] I've read the CONTRIBUTING guide