rustpkg: Make rustpkg commands work without a package ID #7419
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.
r? @brson
rustpkg build
, if executed in a package source directory insidea workspace, will now build that package. By "inside a workspace"
I mean that the parent directory has to be called
src
, and rustpkgwill create a
build
directory in .. if there isn't already one.Same goes for
rustpkg install
andrustpkg clean
.For the time being,
rustpkg build
(etc.) will still error out ifyou run it inside a directory whose parent isn't called
src
.I'm not sure whether or not it's desirable to have it do something
in a non-workspace directory.