chocolatey
Support resumable downloads
I think I've seen this request before, but I can't find it now.
Packages/dependencies could get pretty large and the client may not always have the bandwidth to download all of it at once. Would be nice to be able to resume downloads, perhaps using BITS service.
:+1: Something we want to do. We've just been stuck in the rebuilding aspect for a bit.
I've wrote a package that is using own script to utilize BITS in synchronized mode to resume on every failure of downloads. The code is quite simple and short, easy to understand. You can check it on https://chocolatey.org/packages/vim-tux under Files, in chocolateyinstall.ps1. I wanted to give a pull-request to replace Chocolatey's download code with it, but its original code is quite long and complex with all exceptions that it has to check. It made me be sorry to replace them all with only a piece of code.
Today package size range from 600MB to 6GB. Something happens and I have to redownload a 3GB package on a 2MBps connection. Yeah not everyone siting behind a GB internet connection in silicon valley. Crappy internet connection is still everywhere. Hope the chocolatey team implement this feature as soon as possible.
So I've just discovered Chocolatey and was really excited to migrate to using it for my package management on Windows. However, I was stunned when I noticed that when huge downloads failed, they'd restart from the beginning. This is a major issue... when I use Firefox or a separate download-manager app to manually update my programs I can resume which is vital even on moderately-fast internet connections given the incredibly-large downloads that modern apps often require. Even various Linux CLI package managers support resume. I'm flabbergasted that Chocolately still does not.
We haven't heard any updates about this in over 7 years. The target milestone just keeps getting pushed back year after year. This is a major hold-up and a dealbreaker that prevents me from being able to use Chocolatey as a reasonable solution. Clearly from the comments here I am far from alone.
Any updates re: this ticket? Has there been any progress? Can we know the reasons that 7 years later we still don't have this feature despite chidea having supplied example code? This feature is desperately needed.
