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.
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
fix: use home_path()
in self-update location check
#1242
base: main
Are you sure you want to change the base?
Conversation
It's intentional to not use that here, to prevent breaking pixi installation via package managers.
|
Some cases I can think of are the following (
In the last case, it seems unlikely that package managers would set #779 discusses package manager detection, but that doesn't seem to be implemented yet. Outside of the scope of this "fix" PR, an alternative implementation would be to gate self-update behind an opt-in build-time feature flag that is only enabled on Pixi's GitHub release binaries, but that probably requires more discussion in another issue/Discord. |
Thanks for you write up, I was thinking the same thing as @chawyehsu. But your explanation makes sense to me. I'm going to approve it. @wolfv What do you think? |
Sorry, I realized I made a mistake in my reasoning: |
Just want to point out that in my case this is already happened (I submitted the I don't know if there are other places using |
So that would abort for the same reason that the "non curl" install would abort right? |
friendly ping @chawyehsu |
@ruben-arts Sorry I missed your first ping.
Before this patch, So for instance, I installed pixi (e.g. v0.11.0) with a packager manager that sets This is what @jxu10 talked about in their comment above
Again I'm not completely against this change, since the overwrite will eventually be triggered by the user using I personally won't use |
Now I think Iunderstand it, thanks @chawyehsu! To summarize, the important changes:
I don't mind this new behavior but the warning should help the user a little more.
I think this should include that the $PIXI_HOME was set and because of that it acts like this. (Don't mind the cargo location as that is a development build) |
Since
install.sh
installs to$PIXI_HOME/bin/pixi
, I think it's reasonable forpixi self-update
to match the installer's logic for determining the "default pixi binary path".