This would leave no options to install non-UAC gsudo #271

@ALERTua microsoft/winget-pkgs#131849

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 gsudo --user somebodyElse you'll find out gsudo is not in the path of the target user so you cant gsudo anymore.

So let me ask you some questions.

• Does winget really offers a good portable experience such as scoop?

• Do you know if Winget Releaser (the tool I use to create winget packages) supports portable apps too?
  See

  gsudo/.github/workflows/release.yml

  Line 140 in c23b102

  - name: WinGet Releaser

• I see you are using net46 binaries. Can't x86, x64 and arm64 be used instead? Deprecating net46 was in the roadmap.

Does winget really offers a good portable experience such as scoop?

No, not really, microsoft/winget-cli#549 microsoft/winget-cli#3077 microsoft/winget-cli#222

• Do you know if Winget Releaser (the tool I use to create winget packages) supports portable apps too?

https://github.com/russellbanks/Komac#update-an-existing-package-with-a-new-version

You can just use komac update after manifest is created.

• I see you are using net46 binaries. Can't x86, x64 and arm64 be used instead? Deprecating net46 was in the roadmap.

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.

@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.

After a double-check I can confirm that Chocolatey installs gsudo in a non-portable (with adding PATH) mode at c:\tools\gsudo\current, and the installation freezes if run without UAC while c:\tools doesn't exist. I don't know what scoop even is, so right now, the most convenient way for my scripting is to distribute gsudo.exe along with my scripts. Gotta look into scoop, I guess. Thank you.