-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Feature Request: Choco installer to use same .MSI install as WinGet #212
Comments
This would leave no options to install non-UAC gsudo #271 |
@ALERTua how do you currently use chocolatey to make a non-UAC install? I thougth you were using scoop for that, which works out of the box. @soredake: I appreciate your willing to help here, but creating a winget package is not just the creation of the manifest itself, but mainly updating the release pipeline to do that automatically on each release, and do the testing. Plus, having another installation method means a different 'gsudo experience' (for example, no gsudo powershell module, means worse experience plus updating all the docs), or that with user-scoped installs if you do So let me ask you some questions.
|
No, not really, microsoft/winget-cli#549 microsoft/winget-cli#3077 microsoft/winget-cli#222
https://github.com/russellbanks/Komac#update-an-existing-package-with-a-new-version You can just use
Unfortunately, no, winget needs path to binary in order to create symlink (sudo -> net46-AnyCpu/gsudo) and you can't do per-arch symlinks and there is only all-in-one zip with all binaries. |
After a double-check I can confirm that Chocolatey installs gsudo in a non-portable (with adding PATH) mode at |
Description
C:\tools\gsudo
gsudoSetup.msi
Proposed technical details
The text was updated successfully, but these errors were encountered: