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

.rustup and .cargo are visible on windows #2418

Closed
rbtcollins opened this issue Jul 15, 2020 · 6 comments
Closed

.rustup and .cargo are visible on windows #2418

rbtcollins opened this issue Jul 15, 2020 · 6 comments
Labels

Comments

@rbtcollins
Copy link
Contributor

On windows .FOO does not imply 'hide from the UI'. The Hidden bit is set separately; we should set it. Probably we want to set it and record we've set it in settings.toml to fixup existing installs.

@retep998
Copy link
Member

Directories for applications that are installed normally are not hidden, so there is an argument to be made that rustup should not hide where it is installed. The only reason to hide it is because of the unix convention of dotfiles being hidden and rustup choosing to install to a dotdirectory by default (which is wrong on Windows).

Also, care needs to be taken to ensure that we only hide .rustup and .cargo when they are in the default location and not a user customized location via RUSTUP_HOME/CARGO_HOME.

@rbtcollins
Copy link
Contributor Author

Those are good points; I agree that the installation path is not the normal windows convention, and in fact multirust as rustup used to be known used to be in APPDATALOCAL.

I'll leave this to get some more feedback before proceeding. I'm not sure I agree about only hiding if in the default location; the most common use of those variables we see is folk forcing FHS/XDG style layouts willy-nilly : but I would say that if the overridden path doesn't have a basename starting with a dot, then we clearly shouldn't hide it.

@kinnison
Copy link
Contributor

I think the "basename with leading dot -> set hidden bit" approach is good, I'm kinda feeling like we should just reconcile the hidden bit with the leading dot on self-update, we could do it in the second-half handling so it applies when people update to 1.23 and then remove it again and only set it during installation, or we could always reconcile it on any update. Either is fine with me. I think having an entry in the settings.toml is just overcomplicating things.

@workingjubilee
Copy link
Member

It does seem to make most sense to either follow the Windows convention or, if imposing foreign conventions on others, to impose them in a manner consistent with that foreign convention, rather than devising configuration around it.

@rust-lang rust-lang deleted a comment Jul 17, 2020
@workingjubilee
Copy link
Member

@rustbot label: +O-windows

@djc
Copy link
Contributor

djc commented Sep 11, 2024

Going to close this as a duplicate of #247.

@djc djc closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants