Populate more `env.*` files under `$CARGO_HOME` regardless of platform
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem
It looks like $HOME/.cargo/env is not created on Windows.
This breaks shell scripts that depend on it.
Steps
- Download and run rust-init.exe
- Check ~/.cargo/env existence
Possible Solution(s)
Just generate it like you do on Linux. It's useful for people using native bash on Windows.
Notes
No response
Rustup version
rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.75.0 (82e1608df 2023-12-21)`
Installed toolchains
Default host: x86_64-pc-windows-msvc
rustup home: C:\Users\WDAGUtilityAccount\.rustup
stable-x86_64-pc-windows-msvc (default)
rustc 1.75.0 (82e1608df 2023-12-21)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by running rust-init.exe on Windows and checking whether ~/.cargo/env is created. Trace the installer path that generates environment files across platforms; done means the file exists on Windows and native bash scripts can use it without breaking existing platform behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100