Sam Darwin

> a react-native project I believe currently boost.org and react-native are downloading from two distinct separate locations. Therefore it's an interesting data point to know if you're able to download...

The original jfrog links should be re-activated and working now. It was a mistake on their end. (archives.boost.io used a major cloud cdn)

> what is the recommended source At this moment, the preferred choice is JFrog. The boost website ought to reflect that soon. However... We hope to switch the JFrog hosting...

Hoping to enable the new downloads within the next week if possible, but not guaranteed. At least, check the main website.

Hi @gep13 , This was implemented in issue 586. Comments from there: > like the way PowerShell ignores switches it doesn't understand Well, if I run a powershell script it...

If "new" must be able to take arbitrary switches, then treat "new" differently. Allow that command to have unknown options. We can imagine, that most users are running "choco install",...

> This issue will be closed in 14 days if it continues to be inactive. The "default" behavior of a command line tool should be to verify the provided --option-flags....

> That hasn't been done, and that is why the issue was due to be closed. I had already update the title, from "Verify command line flags" to -> "Verify...

In that case... How about a slightly different alternative then. Instead of modifying ignoreInvalidOptionsSwitches, add a new setting, something like "enable warnings". "enableWarningsInvalidOptionsSwitches". True by default. It will "show warnings...

Hi Nessita, I see that you are taking issue with the word "server". To revisit that particular point, in the original implementation of "sites", where you would hard-code the SITE_ID...