Option to stop uv self update from adding . $HOME/.local/share/cargo/env?

[baggiponte]

Ciao! With rust on my machine already, my shell already sources the cargo/env script. Every time that I upgrade uv to a newer version with uv self update, the line is added to my zshrc and fish conf dir (which I do not use). This is absolutely nothing high priority, but I was wondering if you would consider setting an option to disable this behaviour.

[AbdealiLoKo]

I think you may be looking for --no-modify-path ?

[baggiponte]

I think you may be looking for --no-modify-path ?

Interesting. I don't see it as an option for uv self update though.

[tpgillam]

Seconded - I upgraded from uv 0.4.3 -> 0.4.4 just now with uv self update, and it appended ~/.bashrc with:

. "$HOME/.cargo/env"

I would certainly prefer if the self update command by default did not modify any configuration files. My reasoning is that, if updating, the user has presumably already set their paths in the way that they want (in my case I want my .bashrc portable between different machines, so I don't put any paths directly in that file).

Only a small niggle though. I just have to do a git restore on it every time I upgrade, which is mildly inconvenient at worst!

[baggiponte]

Maybe one could do uv self update --ensurepath or a flag like that and have this behaviour to be opt-in.

[zanieb]

Looking into upstream support for this — I don't think we can add it until they do.

[zanieb]

Can you try setting INSTALLER_NO_MODIFY_PATH=1 during the update?

[tpgillam]

I'm on a different machine today (Fedora 39), where it doesn't try to modify ~/.bashrc, but instead creates or modifies ~/.profile

Can you try setting INSTALLER_NO_MODIFY_PATH=1 during the update?

Yes - this seems to do the trick (installed 0.4.4 and tested on uv self upgrade thereafter).

[zanieb]

Great — we can document that.

[baggiponte]

Confirm too, setting INSTALLER_NO_MODIFY_PATH=1 works :)