Quantcast
Viewing all articles
Browse latest Browse all 9656

Why do Applications Installed through Windows Specific Package Managers seem to Store their Whole Installers Archives in Installation Location

e.g. Vivaldi (WinGet)

As shown above --most if not all WinGet apps seem to follow this trend--, certain apps seem to store themselves or their installer|updater as an archive, within themselves. This sounds like a massive waste of space ; because it is. After purging my system from those redundant archives, I have managed to net a gain of several gigabytes of free space.


Surely you would think that given how these apps were installed through a package manager, they would all exclusively (or at the very least primarily) rely on exactly that in order to get updated, right ?

And yet those are the (only ?) ones I find exerting this sort of behaviour. This is troubling, to say the least.

Is this some kind of WinGet "standard", as in the recommended way of doing things ? What point even is there to keeping an archive of an app --along with its installer-- when the whole point is to update it ; which requires downloading a lot of data regardless.


This sounds like a massive waste, and I would quite like to know the reason behind this choice, if there even are any reasonable ones.

I don't think I've ever seen any other --non-DOS-- package managers do this, nor have any of the previous Windows installation "standards" done anything similar, to my knowledge.


Viewing all articles
Browse latest Browse all 9656

Trending Articles