search

microsoft / winget-cli

WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
https://learn.microsoft.com/windows/package-manager/
MIT License
22.94k stars 1.42k forks source link

Uninstall an installed App #121

Closed denelon closed 3 years ago

denelon commented 4 years ago

As a user I want to be able to use winget to uninstall a package so I don't have to go through the Add/Remove software UX.

Experimental Feature winget uninstall <package> - uninstalls the specified package. winget uninstall -? - displays help for the uninstall command.

Note: uninstall depends on list also being enabled.

winget features - displays all experimental features and their status winget settings - launches settings.json to configure settings like experimental features

Note: There are limitations about how programs get installed and whether or not that binary supports uninstall. This may also need to be supported in the manifest with new key(s) and or syntax.

Edited: experimental status

jthoward64 commented 2 years ago

@denelon > We're not trying to replace any of them.

I'd be... more cautious with that statement. https://keivan.io/the-day-appget-died/

https://github.com/microsoft/winget-cli/issues/353#issuecomment-637016016

Last I'll say on the topic

JanPokorny commented 2 years ago

@keenbowl3009 If you're afraid, don't use winget. Nobody is forcing you. If you want to install PowerShell manually, feel free to go to https://github.com/PowerShell/PowerShell/releases/download/v7.2.0/PowerShell-7.2.0-win-x64.msi and run it yourself, although be aware that you will be doing precisely the same thing as the winget you're afraid of.

Also there is no error, unless you mean the disambiguation note which happens if you enabled the msstore source and thus have two locations to install PowerShell from.

image

JanPokorny commented 2 years ago

@tajetaje Yeah, I know. I just felt the itch to point this out, due to the statement's wording reminding me of this controversy. (Also did the "something to share" already happen?)

keenbowl3009 commented 2 years ago

Also there is no error, unless you mean the disambiguation note which happens if you enabled the msstore source and thus have two locations to install PowerShell from.

There is no error. Unless, of course, there's an error. Then the error is a feature!

keenbowl3009 commented 2 years ago

@keenbowl3009 If you're afraid, don't use winget. Nobody is forcing you. If you want to install PowerShell manually, feel free to go to https://github.com/PowerShell/PowerShell/releases/download/v7.2.0/PowerShell-7.2.0-win-x64.msi and run it yourself, although be aware that you will be doing precisely the same thing as the winget you're afraid of.

Also there is no error, unless you mean the disambiguation note which happens if you enabled the msstore source and thus have two locations to install PowerShell from.

image

I have not "enabled" mstore. It get's enabled by itself, automatically. Absolutely no input on my side.

keenbowl3009 commented 2 years ago

If you are getting a error installing something, open a ticket. Things can't get fixed if the devs don't know of the issue

Thanks. https://github.com/microsoft/winget-cli/issues/1711

JanPokorny commented 2 years ago

@keenbowl3009 Using command line package managers requires a basic degree of computer literacy, including the ability to comprehend bright yellow text in simple English. I am afraid that I can not help you further, sorry.

Masamune3210 commented 2 years ago

If you already had a ticket, what was the point other than to scratch the chip on your shoulder you seem to have of bringing it up. I'm done. Its obvious you arent acting in good faith and just want to stir up trouble

EqualDust commented 2 years ago

IMHO it is a dishonest attitude closing this issue since the uninstaller is currently broken and most of the time does not work.

JanPokorny commented 2 years ago

@EqualDust The feature is implemented, that's why this issue is closed. It can certainly be buggy for some uninstallers -- the correct attitude to fix this problem is to report each individual bugged uninstaller.

Also, stop creating new GitHub accounts, please.

EqualDust commented 2 years ago

every bug is a new account. Reporting each individual bugged uninstaller is inneficient, an org with resources like msft should be able to ship great products by default.

How come scoop, completely community backed, get this right by default?

Mallchad commented 2 years ago

Please don't make an ordeal of this, the topic of the issue has been resolved, if you have an issue (and I don't doubt you have), it is correct to make a new issue.

This thread is getting long and very noisy now, noisy threads are hard to follow. Are you will be bothering people that are still inadvertently following a virtually dead issue.