Open
Conversation
85565d4 to
4a74287
Compare
29a2f48 to
7fb31c5
Compare
7fb31c5 to
a34c4a1
Compare
Author
|
Still pending: how to document use of pixi? Add to README? What I do is usually either
but not sure how to fit it best in README without making it confusing with current instructions |
Collaborator
This could fit very well inside the wiki. Do you have the documentation already prepared? You can send it to me or @jermp, or write it as a comment here, and we will add it right away. |
This file contains hidden or 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
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.
While working on conda-forge/staged-recipes#28343 I created a pixi configuration for local dev, submitting here as a PR.
This might help with #45 too, we use in some parts of sourmash CI and it is very convenient because it uses the same deps from local dev.
I tested this in
/usr/sbin/softwareupdate --install-rosetta --agree-to-license)the github actions workflow uses this pixi configuration to do a build and run the generated binary, but I can't test it properly because I don't have permissions to run GH actions in your repo