docs: improve README.md manual installation technique, fixes #296

[rfay]

• README: Manually: Unzip the latest release, and add to the path. #296

Just adds some more detail to the manual install technique.

[gerardog]

Thank you rfay!

[rfay]

Thanks for this great tool.

[rfay]

BTW, I think we'll end up doing two installers, one aimed at choco, which does not include gsudo; the other will include gsudo bundled and will be the one we offer for "normal" download. Then there won't be a download at install time.

[gerardog]

Are you sure you want to go thru so much trouble?

• Arguments for embedding it:
  • It is unlikely that gsudo will be flagged as a virus in the future if you follow these rules. There is a 30-day window since a new gsudo build is uploaded until it gets popular enough (gaining reputation on AV scanners). The first day generally gets a score of 1/60 or 2/60... which drops to 0/60 after a few weeks. The mistake made by chocolatey by considering 1/60 low score as dangerous was already fixed and should not affect your software packaging, in my opinion.
  • You may include a well-known gsudo.exe in your distribution, and if you update it, you can always pick one that is already has a low score.
• Arguments against embedding it:
  • gsudo does not handles gracefully having more than one binary in use, as the credentials cache rejects connections from another .EXE files.
  • gsudo experience is not the same on WSL/bash without the wrappers... (I would install not just gsudo.EXE)

But putting myself in your situation... I would:

• Trigger the independent installation of gsudo, a) as a post install task or b) during DDev first run
• In DDev: before invoking gsudo, handling what happens if gsudo is not installed:
  • a) just trigger the installer. Your app just need to call this line PowerShell -Command "Set-ExecutionPolicy RemoteSigned -scope Process; [Net.ServicePointManager]::SecurityProtocol = 'Tls12'; iwr -useb https://raw.githubusercontent.com/gerardog/gsudo/master/installgsudo.ps1 | iex"
  • b) you can always just start an elevated process with 'verb=runas' as a fallback for those outliers rejecting to install gsudo...

[rfay]

Thanks for the good thinking, I sure appreciate it.

You may include a well-known gsudo.exe in your distribution, and if you update it, you can always pick one that is already has a low score.

So just explicitly use an old one with a good virustotal score? How would I figure that out?

[rfay]

Linking to the DDEV PR to show what actually ended up happening and so we can find these various (great) discussions:

• build: use gsudo.exe directly from gerardog/gsudo, for #4701 ddev/ddev#5314