Package linux SDK shell scripts also into windows SDK for use with msysgit

[DartBot]

This issue was originally filed by @friegger

---

What steps will clearly show the issue / need for enhancement?

1. Running pub from msysgit does not work
2. Copying the pub.sh from the linux SDK to the dart-sdk/bin folder solves this.

What is the current output?
Cannot find pub

What would you like to see instead?
Pub executing

What version of the product are you using? On what operating system?
1.5.x

Please provide any additional information below.
To work with git on windows many use msysgit. It's basically a bash environment that provides everything required to run git. While already working in this bash, it would be convenient to be able to execute all script based tools from the dart-sdk as well. Please consider to package all the sh scripts also in the windows SDK.

I have only tested the pub.sh from the linux SDK and it just works.

[anders-sandholm]

Added Area-SDK, OpSys-Windows, Triaged labels.

[DartBot]

This comment was originally written by [email protected]

---

Would be a great improvement indeed.

For those who cannot wait, download

https://raw.githubusercontent.com/dart-lang/bleeding_edge/master/dart/sdk/bin/pub_sdk

rename it to "pub" and put it into

C:\Program Files\dart\dart-sdk\bin

Works for me, at least.

[DartBot]

This comment was originally written by @Emasoft

---

Or even better: write those scripts directly in Dart. Dart should already have implemented crossplatform I/O functionality, polyfilling any difference betwen Linux, Win, Osx, ChromeOS, etc.
Dart is an excellent shell scripting language, much better bash or python. It's time we start using it as a standard script for all things.

[DartBot]

This comment was originally written by @seaneagan

---

Also for cygwin, see issue #20822.

Currently I have to run pub.bat ..., since pub ... doesn't work, and same for any pub global activated scripts (oops, I mean pub.bat global activated), I have to run those as e.g. script.bat instead of just script. This also means that I can't write a cross-platform bash script which calls any of these things, and works locally in windows and in my CI/deploy targets/non-windows dev envs.