Discovery: initial py-rattler-build integration for v1 recipe support #5858
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
Investigate integrating py-rattler-build bindings to enable conda-build to support both v0 and v1 recipe formats, with automatic delegation to rattler-build for v1 recipes.
Why is this needed?
The conda packaging ecosystem is evolving with the introduction of v1 recipe format. To ensure a smooth transition and maintain ecosystem compatibility, we need a bridge that allows users to work with both formats through a single interface. This enables gradual migration from v0 to v1 recipes. A unified conda-build interface that delegates to appropriate backends based on recipe format provides a clear upgrade path for the community.
What should happen?
Conduct a discovery phase to evaluate py-rattler-build API for key workflows including recipe format detection, variant discovery and expansion, recipe rendering, and build execution. Write-up / prototype how we would unified interface that transparently handles both recipe formats and delegates to py-rattler-build for v1 recipes. This should include steps that we would take to start to implement this.
Additional Context
The Prefix team has shared early Python bindings available at:
git clone https://github.com/prefix-dev/rattler-build.git
cd rattler-build/py-rattler-build
git switch refactor
pixi run edit-notebook notebooks/1-recipe_rendering_basics.py
CC: @wolfv, @Hofer-Julian, @jsmolic, @jaimergp