-
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
Add a flag to install/upgrade packages without creating desktop shortcuts #1045
Comments
And have an option to designate destination for the shortcut, maybe the user uses the Quick Launch folder. |
Some installers don't have switches to not create a desktop shortcut/start menu shortcut, it is only possible by using interactive installation but that defeats purpose of using winget. Some installers don't even give option to not create desktop shortcut. In Here is what it should look like in
These fields should contain wherever the installer creates following shortcuts. Person who submits the package needs to take care of that.
As |
Deleting files on the users machine seems rather risky, the manifest schema must enforce a specific list of approved root shell folders. Maybe just Start menu, Start Menu\Programs and Desktop. Winget would also have to check the creation date of the shortcut to make sure it only deletes new shortcuts created after Winget started. Without bothering to look it up, I would assume that there is a Windows Logo requirement or recommendation that installers should not create shortcuts anywhere except under "Start Menu\Programs". Installer authors should be encouraged to follow reasonable guidelines. |
Adding to the complexity
|
I haven't invested enough time to know how reasonable this feature is. I'll flag this as "Area-Settings" and "Area-Manifest" so it shows up in searches when we're looking at settings and schema changes. If someone could provide a couple of examples for packages that support this in "silent" mode, and some that don't, we can have a couple of packages to evaluate edge cases and the impact to user experience and expectations. The manifest would need to inform us what a package does and does not support. Generally, when we add arguments and settings, things get tricky. If a user requires the behavior, it's likely to impact how many packages a user could successfully install. We would also likely want to look at the search experience if a user requires this ability so we wouldn't show them packages they couldn't install. |
An optional entry in the manifest that some developers can fill.
Most installation programs have this option, so I think this would be easy
for developers to use, or to ignore.
|
Inno Setup: NSIS doesn't have official switchs for shortcuts, so it rests with installer authors. 🤷 So does EXE |
Thank you.
Let's see if some developers take advantage of this.
|
Description of the new feature/enhancement
Add a new flag to give the user the option to add/ upgrade a package without creating a desktop shortcut
I think there are many people out there that, like me, love to keep their desktops clean, without any shortcuts.
So every time I run "winget upgrade --all" I need to go to the desktop and manually delete all the created shortcuts.
The same happens when adding a new package or upgrading a specific one.
What I do believe will help a lot it's a new flag. Something like "-ns"(no shortcut). So the final command should be something like "winget upgrade --all -ns".
Proposed technical implementation details (optional)
At this point, I don't know the complexity of this task in terms of implementation.
The winget-cli is already an amazing tool and I like it a lot. I believe this feature could make the winget even better, but again, I don't know how complex it could be as every installer is different from the others.
The text was updated successfully, but these errors were encountered: