Move installable targets out of uv-resolver crate
#10126
Draft
+185
−141
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
charliermarsh
added
the
internal
charliermarsh
force-pushed
the
charlie/installable
branch
2 times, most recently
from
e9d2f23 to
cef42c0
Compare
charliermarsh
force-pushed
the
charlie/installable
branch
from
cef42c0 to
3e31c52
Compare
charliermarsh
added
no-build
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
The proximate motivation is that I want to add new variant for scripts, but
uv-resolvercan't depend onuv-scriptswithout creating a circular dependency. However, I think this does just make more sense -- the resolver crate shouldn't be coupled to the various kinds of workspaces, and these details are mostly encoded inprojects/lock.rsand similar files.