This is an interesting idea. I think it might clash a bit with what we do in pixi though (where we will also have source dependencies like this, and the ability to depend on other packages by git or path).

We need to think of a way to do this that will have a good user experience. And we would also have to orchestrate builds in a way similar to what we are currently implementing in pixi.

On the other hand, what users can do today is that they can checkout the git repositories they are interested in manually, and then merge them all into a recipe-dir from which all packages will be built in the right order.

Hi @wolfv! I was the original requester for this.

The use case I'm hitting is using the pixi-build-rattler-build with pixi-build. I have other packages that also use that same setup, but they can't easily depend on each-other in a clean way without publishing them as conda packages. It would be really nice to be able to set up deps without having to publish to a conda channel.

That's really good to know about the recipe-dir, is there an example of that being done somewhere in a recipe.yaml file that I could check out?

My use case is the Mojo ecosystem. I spent a little bit of time trying to implement a mojo-build backend, but realized I just don't know enough about pixi yet to do that, and Mojo already uses rattler-build for modular-community.