-
Notifications
You must be signed in to change notification settings - Fork 106
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
Save cached releases to standard directories #24
Comments
What do you propose to do with the existing cache directory? Is that still taken into account? |
We could use the old location if it exists or move the old location to the new location. At Greenkeeper the moving is done. Both have their own pros and cons. |
@malept any preference for one of the solutions? |
I would prefer moving it. |
@Siilwyn I see error in your merged changes, that leads to #47 (comment) Code
in the But! We call In version of electron-download that used by electron-builder, I will remove this code for now. |
Oh that is bad. :/ @develar could you expand your explanation? I don't quite follow: |
@Siilwyn downloadZip calls cachedZip, but cachedZip will check and return old location. Not evident how does it lead to error, but in any case it is not good — cachedZip should return constant result (based on options) and old location should be checked in another place. |
The function that checks if the zip file is already cached sounds like the appropriate place for this check to me. Where would you place it? Edit: I replicated the error @develar, will debug it! |
@develar moving the logic to the directory location seems to fix it. Could you confirm this? |
Instead of placing the release archives in the home directory they should be placed in the appropriate directory per OS. I've done the same for Greenkeeper's RC so I'd like to create a PR for it.
Before doing that I'd like to know if there are any special things I should take into consideration and if the core contributors are on board with this so I don't do it in vain. :)
The text was updated successfully, but these errors were encountered: