Skip to content

docs: clarify which installation method to use for local development #5392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Hofer-Julian merged 1 commit into from
Jan 24, 2026
Merged

docs: clarify which installation method to use for local development #5392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,15 +204,15 @@ cargo install --locked --git https://github.com/prefix-dev/pixi.git pixi
We don't publish to `crates.io` anymore, so you need to install it from the repository.
The reason for this is that we depend on some unpublished crates which disallows us to publish to `crates.io`.

or when you want to make changes use:
If you install pixi that way, it isn't necessarily the first in your PATH.
The one installed by the installation script might take precedence.
Therefore, we recommend running the following task instead for local development:

```shell
cargo build
cargo test
pixi run install-as pixid
```

If you have any issues building because of the dependency on `rattler` checkout
it's [compile steps](https://github.com/conda/rattler/tree/main#give-it-a-try)
This way, a new binary called `pixid` will be available without any name conflicts with other Pixi installations on your system.

## Uninstall

Expand Down