fix: Prepend pixi to path instead of appending #1644
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You are right about the .bash_profile. Lets also remove that. |
|
changes updated |
ruben-arts
approved these changes
Jul 22, 2024
|
This broke my workflow... It could be something silly on my part - any ideas appreciated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR changes how pixi is added to
PATH. The value is prepended so that pixi takes precedence. This is similar to conda so that they libraries/tools installed via pixi take precedence.part of #1058
I would also like to discuss the lines above regarding adding to
bash_profile, why not just add to.bashrcsince it will be sourced by.bash_profileanyway. This will also allow the usage on both login and non login shells.