-
Notifications
You must be signed in to change notification settings - Fork 170
Windows PATH separator wrong in Chef exec command #180
Comments
Yeah there were two different issues in one ticket, serdar closed it after appbundle'ing foodcritic, but the path fix got dropped |
👍 Would be great if someone can get a PR for this 😄 |
I think this is the code change, it just needs specs: |
That's correct - the change works on my box. |
^ that needs a spec and a changelog update, i've got higher priority things i'm working on for several days |
@irvingpop Does this address the known issues you called out in your blog post? |
Question - should GEM_PATH use |
I think it should be semicolon in PowerShell, colon in Bash (on Windows) |
GEM_PATH should only be consumed by ruby |
Confirmed: powershell:
bash:
|
I think the scenario we want to ensure is:
|
FYI - I get the following errors running the rspec for 0.3.0 on Windows Powershell. These make it hard to resolve if I'm seeing different errors with this fix. I do have a couple of fixes for some of these that I can submit, but most of them would require more in-depth analysis than I have time for at the moment. (Edit: see #225)
|
From Chef-dk 3.0 windows 7 box
From comment here:#165 (comment)
Comment:
Correct, this line needs to be using the ruby File::PATH_SEPARATOR constant: https://github.com/opscode/chef-dk/blob/7c4f55cd1665727203aef211bb3e5931d2ac8547/lib/chef-dk/helpers.rb#L86
Also it looks like we are mangling all the ";" within the path as well, sample output (Notice all ":") :
The text was updated successfully, but these errors were encountered: