Isuru Fernando
Isuru Fernando
Edited my suggestion
For clang, we'd need `clang-conda-cfg_linux-64` etc and it won't be the same. The issue with the name `gcc-conda-specs` and `gcc-no-conda-specs` is that it feels like they are opposites of each...
No, `conda-gcc-specs` doesn't include the unprefixed gcc.
I really don't like that suggestion. The symlinks should stay in `gcc`. It would be too confusing if it was any other way.
I think for conda-build, the conversion of strings to booleans should happen in jinja as well. For rattler-build, I think we shouldn't convert types and keep them as is.
@conda-forge-admin, relint
@timkpaine, can you confirm?
@conda-forge/help-c-cpp, @traversaro @wolfv this is ready for review