Packages which are there in MS Store should be removed from here #29985
-
There are some packages which are present in Microsoft Store as well as in this repository. The question is "Should we remove these packages from here to avoid duplicate conflicts while running |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
We have been discussing catalog deduplication. We still need to improve matching in the "msstore" source, and a couple of other Issues: https://github.com/microsoft/winget-cli/issues?q=is%3Aissue+is%3Aopen+label%3Amsstore One of the other challenges is the store only retains a single current version. If these packages are removed from the community repository, the historical versions are no longer available. That may be fine for the vast majority of packages, but some of the developer tools may need to be retained. |
Beta Was this translation helpful? Give feedback.
-
Also, some packages use different installers for their Microsoft Store deployments (even for Win32). VSCode uses some weird bootstrapper so they don't have to update the Microsoft Store for every release, for example. (Of course, Win32 apps should be retained indefinitely since Windows 10 can't install them from the Microsoft Store). |
Beta Was this translation helpful? Give feedback.
-
I am not talking about Win32 apps since they aren't supported on Windows 10 until a big update comes for Windows 10 which won't happen probably (2/10 probability). Packages like " |
Beta Was this translation helpful? Give feedback.
-
I personally don’t think its an issue because we know there will be some form of default Behavior when Multiple Sources are Configured. I personally would rather use the version from the community repo than the one that is in the store, even if they are exactly the same. I’m sure others would rather use the one from the store. I believe having it available in both sources would be more beneficial, since it would give more choice to the users |
Beta Was this translation helpful? Give feedback.
-
I didn't saw that. If a user can set priority on sources, then it is probably fine. |
Beta Was this translation helpful? Give feedback.
We have been discussing catalog deduplication. We still need to improve matching in the "msstore" source, and a couple of other Issues:
https://github.com/microsoft/winget-cli/issues?q=is%3Aissue+is%3Aopen+label%3Amsstore
One of the other challenges is the store only retains a single current version. If these packages are removed from the community repository, the historical versions are no longer available. That may be fine for the vast majority of packages, but some of the developer tools may need to be retained.