Open travnick opened 9 months ago
I think that the —no-cache
expected behavior is to not read from the cache, not to avoid writting to it.
What's the point of writing to cache if it's not read? I feel like both read and write should be disabled or read/write flags introduced.
The point of this option is to force the redownload, in case an app have been updated without its version changing for example
So good name for current behaviour is --redownload
.
Thing --no-cache
suggest to not use cache at all. No read, no write. Not writing a cache helps with saving space and reducing unnecessary files while creating containers or other scenarios.
Bug Report
Current Behavior
There are cache entries after run
install
with--no-cache
optionExpected Behavior
There are no cache entries after run
install
with--no-cache
optionAdditional context/output
Possible Solution
System details
Windows version: 10.0.19045.3693
OS architecture: 64bit
PowerShell version: None - run with cmd
Additional software:
Scoop Configuration