Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add target_dir for 3rd party subcommands #9805

Closed
wants to merge 1 commit into from

Conversation

Firstyear
Copy link
Contributor

@Firstyear Firstyear commented Aug 18, 2021

This allows third party subcommands to see the target dir
environment variable as cargo has processed it from the workspace.
Due to moving the processing to ops, this also allows further
variables to be exposed to subcommands in the future.

Fixes #9804

This allows third party subcommands to see the target dir
environment variable as cargo has processed it from the workspace.
Due to moving the processing to ops, this also allows further
variables to be exposed to subcommands in the future.
@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Eh2406 (or someone else) soon.

Please see the contribution instructions for more information.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 18, 2021
@alexcrichton
Copy link
Member

Thanks for the PR. I left a comment on the issue about how I don't think this fits the subcommand abstraction.

@Firstyear Firstyear closed this Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RFE: expose target_dir as an environment variable to 3rd party subcommands
4 participants