You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the point is that there is no installation. Where to unpack is up the everyone's use case, preference, or permissions. Another optional step is adding that location to PATH.
For those uncertain doing these manually, it's probably easiest to rely on winget, scoop or Chocolatey, which make these steps automatic and use their own locations to make it work as a one-step process. These package managers all use curl-for-win binaries under the hood.
That said, I'd be happy linking to a document (a curl wiki page?) that's community maintained.
I think it would help to add a sentence stating that "Windows users should generally wait for Microsoft to update curl via standard Windows Updates". The Curl executable is a trusted system file and not easy to replace or update.
Yes, overwriting the base OS, including its bundled curl.exe with any other curl is strongly not recommended. Unzipping the archives distributed here will never overwrite those.
Windows forks are most likely to install via a package manager or setup executable.
Many Windows users will be unsure where to put curl.exe from the zip file: app/roaming/or Windows/system 32, etc...
It would be nice to have instructions or a pointer to same in the readme or downloads page.
Thx!
The text was updated successfully, but these errors were encountered: