Zanie Blue
Zanie Blue
I don't really know how to test this.
Okay so... testing this out ``` cargo dist build npx http-server -o ./target/distrib ``` then edit the installer to use `ARTIFACT_DOWNLOAD_URL="http://127.0.0.1:8080/target/distrib/"` give a happy installation at the new location ```...
Some pain points: 1. There's no warning if the newly installed `uv` is not first on the path, i.e., another uv binary will be used instead of the one I...
Requires some docs changes still
> For my own understanding, where does `$XDG_DATA_HOME/../bin` come from? (I know we check this already.) `XDG_BIN_HOME` isn't officially a part of the standard. So it's sort of a "next...
Regarding `env` — yeah it's not great, but it doesn't shadow the `env` executable because it's not executable ``` ❯ PATH="/tmp/bin:$PATH" which env /usr/bin/env ❯ /tmp/bin/env zsh: permission denied: /tmp/bin/env...
In favor of what? It still needs to go somewhere for activation purposes right? My main concern is that it could collide with another `env` file in that directory, but...
It's what they use for adding the install directory to the `PATH` in shells without duplicating the entry, e.g., in my `.zshrc`: ``` . "$HOME/.cargo/env" ```
As far as I understand, it's the same as the existing behavior (just in a flat directory, which honestly makes more sense to me anyway). ``` ❯ export XDG_BIN_HOME=/tmp/example-bin-home ❯...
Ah I thought you meant did the `env` script duplicate the entry. No, it looks skips creating the `env` files and modifying the shell config at all: ``` ❯ export...