List view

• Initial `pixi build` implementation

  `pixi build` is going to be our source -> package command. Our current design is tracked in https://github.com/prefix-dev/pixi/issues/1654 ## Main goal Let users create a `conda` package from their pixi project. ## Key wishes - No lock-in by build tool, let users define what build tool they want to use. - Let pixi depend on the built packages as a separate `path` dependency (workspaces) - Initial goal is `conda` packages but the design should not limit to that format. Before the first release we'll merge into the [`feature/pixi-build`](https://github.com/prefix-dev/pixi/tree/feature/pixi-build) development branch. To allow for non breaking releases while this is being build.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed

• New `pixi global`

  While we love `pixi global` for the simple tool installer it currently is. There is a set of improvements we've envisioned for it. ## Main goal Let users create more flexible global environments and make it easier to share/save the setup for other machines. ## Key wishes for `pixi global` - A manifest file for all global environments/tools. ( ~ https://github.com/prefix-dev/pixi/issues/1280) - A command to sync the "global" manifest with the environments. - Multiple packages in one "global" environment. (https://github.com/prefix-dev/pixi/issues/342) - Letting users specify which binaries to expose per environment. (https://github.com/prefix-dev/pixi/issues/1017) _This milestone will be used to group issues and PR's_

  No due date

  •26/28 issues closed
  92% complete2 open26 closed