-
Notifications
You must be signed in to change notification settings - Fork 892
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
cache clean command to remove temporary files #1124
Comments
Duplicate |
So I thought this was a dupe - we've discussed this and have been planning for awhile. I'm surprised there is not an actual issue filed already. Edit: chocolatey-archive/chocolatey#253 (linking this to that and closing that issue). |
Please elaborate |
The lot of temp files are cleaned up - change your cacheLocation config value. Then temp is more deterministic and things are cleaned up better |
I just did |
Ah, cached installers. Not package versions left behind. |
Right, they can be hundreds of megabytes, and scattered across dozens of users' temp folders. Also why not use a global location for cached installers if chocolatey is installed globally? Or better yet, once downloaded, move the cached installers to a cache folder in chocolatey's folder? Either way a |
Re: Global location - did you miss my response on setting a global temp location by setting the cacheLocation? |
I have 2 GB of cache files. Is it safe to delete everything manually? |
@07416 yes, apologies if that is not clear. As long as you are not saying you have 2GB of files including nupkg files in what you consider cache - the "%ChocolateyInstall%\lib" location is not what we would consider cache in this case. |
@ferventcoder The location is |
Yep, that's fine. |
Any update on this im a new user and also noticed that all temp files are there, if they are not needed after an install success there should be a switch to delete or better still some sort of a clean command... :) |
@mitchmenghi This was implemented in Package Reducer, which also comes with This is still on the backlog and determination for how it will be released. |
You can also look at https://chocolatey.org/packages/choco-cleaner/0.0.1 EDIT: BETTER link: https://chocolatey.org/packages/choco-cleaner |
I'm glad that I've come across this issue. I'm testing Chocolatey and my @ferventcoder, I understand that automatic package reduction is a killer feature of the licensed version, however would you please consider releasing at least the cache cleaning command on the community edition? I'll be glad to buy the pro version or donate to help you keep the good work in Chocolatey. However - and please take this as constructive feedback - all major package managers that I can think of have some kind of |
Really? This is a premium feature? |
Why does that package show as rejected? |
@07416 I'm glad you brought that up! Anyone in the future reading this thread, please click the following link to jump directly to the current release: |
Looking forward to having this feature in the free version. |
I agree with others here. The paid version should have features the free version doesn't, otherwise no one would used the paid version and funding would dry up. However I also feel that cache cleanup is a basic part of any package manager. Maybe a good middle ground would be to have basic cache cleanup (clearing the temp folder) in the free version, and to have all the other reducer/optimizer stuff (reducing NuPKG size, etc) continue being a paid feature. Basic cache cleanup is good for users and it can go a long way in making Chocolatey more favorable in the eyes of users. That's just my two cents. I thank you all for all the work you do on Chocolatey, and I appreciate having Chocolatey to use. I will always continue to support y'all anytime I can afford to, and I hope y'all keep up the great work! |
chocolately creates lots of temporary/cached files when installing packages, and these aren't removed when the installation is complete. Even older version aren't removed. Chocolately needs a
cleanup
command that tells it to delete all its temporary and cached files.Editor's note: The original issue was filed at chocolatey-archive/chocolatey#253
The text was updated successfully, but these errors were encountered: