@conda-forge-admin rerender

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

• License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

Not really. I checked and they use a cos7 based docker image, so they would still get sysroot_linux-64=2.17 by default

How does that work? I guess the runtime constraint on glibc?

I guess the runtime constraint on glibc?

Yes

The other way we had wanted to work on this was to enable a "system" sysroot where our compilers would use whatever sysroot is available on the system itself.

Thanks Isuru! 🙏

FWIW think this would be a great improvement for users leveraging our toolchain in development environments

Matt makes a good point about having an option to use the "system" sysroot. IIUC we could make that change as well. IOW this change shouldn't limit it us in enabling that option in the future

As to Bioconda, see Isuru suggested moving to {{ stdlib("c") }} in issue ( bioconda/bioconda-recipes#51185 ). Looks like they had some hangups with linting. Though don't have any more details as the log they shared expired. Perhaps once someone includes fresh details there, we can learn how much of a lift it would be for them to add use {{ stdlib("c") }}