-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
User should define what kind of packages can be installed / can be listed #304
Comments
This looks loosely related to #154. I only mention it as we would likely use that work item to make sure we have the ability to manage the client. This would be a feature to allow or disallow a subset of installer types. |
[Policy] Area-Settings |
We've added support to specify the installer-type when installing packages. The remaining work would be to make a section in settings to specify required installer types. |
I do believe that the settings portion already exists - however, it only applies to the install command and does not affect |
Description of the new feature/enhancement
The tool should have a configuration that prevents specific kinds of installers. E.g. WinGet could configured to only install MSIX and not MSI packages.
The problem I have with currently existing package manages or precisly the managed packages under windows is that I don't trust there uninstall. While MSI can be correctly uninstalled and often will, in my experience it does not always works. Using a package manager hides the fact what install medium is used. (It is not that I never install software that uses MSI but I generally think twice about it)
If I could setup winget in a way that it lists only packages that are known to uninstall/update without problems I head much more confidence in using it.
This way MSIX (and maybe other formats that can be easily removed) can be promoted a little bit without loosing support for "older" software.
The text was updated successfully, but these errors were encountered: