-
Notifications
You must be signed in to change notification settings - Fork 168
Add support for a Windows environment without true/false #240
Conversation
👍 |
@opscode/client-engineers ? |
Do we really need powershell to have a command that exits 0 or 1 on windows? |
We could do the same thing with cmd.exe, which is probably a bit more lightweight. We should reliably have both cmd and powershell on a system already, whereas the existing code requires us to either install a tool or include embedded\bin in the PATH (which contains a false/true) which we keep flipping around on. Wherever we stay with the PATH, it's nice if we don't need it. |
@btm does can we use ruby? |
@jdmundrawala |
@tyler-ball it would have to be |
@danielsdeleo 👍 yup, that worked |
Ruby was surprisingly fast. I expected it to suck on windows. It's 2-3 times faster than loading powershell:
|
Although cmd.exe appears to be slightly faster (once I got the right quotes)...
|
I think the benefit of using ruby is that we only have to maintain 1 code On Wed, Nov 19, 2014 at 8:55 AM, Bryan McLellan notifications@github.com
|
If |
We don't always have true.exe / false.exe on Windows, especially if we don't have the embedded bin directory from the omnibus package in our path.
e1e4468
to
d319133
Compare
|
👍 |
Add support for a Windows environment without true/false
We don't always have true.exe / false.exe on Windows, especially
if we don't have the embedded bin directory from the omnibus package
in our path. This patch uses powershell + exit to simulate the same thing.
Fixes a number of failing tests. /cc @jdmundrawala