Wolf Vollprecht
Wolf Vollprecht
Thanks @erik-bershel !
Amazing work writing all this up. I am halfway through and I have the following comments: - I was thinking it might be useful to have an `build_to_host_and_run` as well...
at this point you are just reinventing conditional dependencies in a worse way though :)
I had another think on this and while this could be solved as conditional dependency, it could still be listed under `build_to_build`. Since we have run-exports available from the repodata...
Maybe @h-vetinari can comment on wether we need to set both values or if one should be enough. I am not sure!
I believe you need to set both. But I am verifying with @h-vetinari and others. Thanks for testing!
I think I understand what happens: - staged-recipes detects the `conda_build_config.yaml` fine, and writes the additional deployment target key by appending to the `conda_build_config.yaml` file. - rattler-build does _not_ automatically...
Yes, with `variants.yaml` the problem is that in staged-recipes the automation only looks at `conda_build_config.yaml` so it will never "magically" add the `MACOS_DEPLOYMENT_TARGET`...
It's not fixed yet. We either need to support `variants.yaml` in conda-forge, or we need to support `conda_build_config.yaml` in rattler-build. :)
We support `conda_build_config.yaml` files now, so I think this is fixed.