Skip to content

pub uses %APPDATA% and not %LOCALAPPDATA% #1273

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

Closed
DartBot opened this issue Jun 5, 2015 · 2 comments · Fixed by #2297
Closed

pub uses %APPDATA% and not %LOCALAPPDATA% #1273

DartBot opened this issue Jun 5, 2015 · 2 comments · Fixed by #2297
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Jun 5, 2015

Originally opened as dart-lang/sdk#22954

This issue was originally filed by [email protected]


What steps will reproduce the problem?

  1. Check pub's cache dir on Windows OR
  2. Check pub global's exes dir on Windows

What is the expected output? What do you see instead?

Stuff is stored in %USERPROFILE%\AppData\Roaming...

i. e.

%APPDATA%...

Because pub does not store configuration data, but cached data and scripts, it seems strange that pub stores stuff in the roaming profile, as Dart many not be installed on other computers the user accesses. It seems more adequate to store the cache and pub global exes in the %LOCALAPPDATA% folder.

Note that if config data was stored instead, it would be more justifiable to use %APPDATA%.

What version of the product are you using?

1.8.5

On what operating system?

Windows

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

<img src="https://avatars.githubusercontent.com/u/2108507?v=3" align="left" width="48" height="48"hspace="10"> Comment by dgrove


Added Area-Pub, Triaged labels.

@DartBot DartBot added the type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) label Jun 5, 2015
@nex3
Copy link
Member

nex3 commented Dec 4, 2015

This does sound wrong, but just changing to %LOCALAPPDATA% may be painful to users who have globally-installed executables and so forth. One possible strategy would be to prefer %APPDATA%\.pub-cache if it exists, but start creating new caches in %LOCALAPPDATA%\.pub-cache. We could even have pub cache repair move from the old location to the new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants