Standardizing Cargo command execution#284
Merged
ivila merged 2 commits intoapache:mainfrom Mar 3, 2026
Merged
Conversation
Signed-off-by: ivila <390810839@qq.com>
Signed-off-by: ivila <390810839@qq.com>
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
1 participant
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.
Since cargo-optee is a Cargo plugin, it inherently requires a standard Cargo installation, which allows for a much cleaner execution model.
This PR streamlines the codebase by removing the legacy logic used to manually detect the Cargo binary and configure the PATH environment. Instead, it now follows standard plugin conventions by reading the CARGO environment variable, ensuring the tool consistently invokes the same binary that called it without requiring any manual environment setup from the user.