Open question: what would you like to see from a Mojo package manager?

Mojo
26

Great to hear from your Wolf!

I’m a pixi fan and I’d love the community to adopt pixi as the “blessed” modular package/env manager. pixi-build works quite well and I’ve had no issues with it building from source with git and it’s quite fast building multi-packages with multi-languages invovled. Unfortunately (the community built) pixi-build-mojo doesn’t as it uses mojo package which is unstable and tied to a very specific compiler version (we’ll be renamed soon that better shows this Proposal: rename `mojo package` and `.mojopkg`) so if there’s a dependency that uses different mojo version it’d fail to work as .mojopkg for 1.0.0 is different from 1.0.1.

My wish list for now:

  • The ergonomic should be better and I wish I didn’t need to write recipe.yaml (and maintaining its own version) if I’m not customizing my build and have normal dependency specification in pixi.toml similar to cargo.toml. I understand that packages that have multiple languages involved may need such lang-agnostic recipe but if my dependency knows how to deal with them then downstream packages should just work without repeating them in recipe.yaml.
  • Also would be great to optionally support similar build.rs-like script that’s language specific and in mojo case can be build.mojo as an idea!
  • Besides, nested workspace-like packages are harder to work with than cargo which I think the UX can be improved without manually specifying the manifest path for example.
  • Better way to enforce system level requirements as well as gpu vendor and arch support which is important for mojo