Attempt to work with different quoting styles that worked in previous client

[thigg]

The currently working method to use the current path is "%cd".
At least here:
https://github.com/chocolatey/choco/wiki/CreatePackages#testing-your-package
The documentation suggestes '%cd%'

*From Rob: * Some of the documentation was plain wrong and leaned towards cmd.exe - single tick marks have probably never worked in powershell.exe that I'm aware of. That's why the '"stuff"' (apostrophe followed by a double quote) in some parts of the documentation.

[ghost]

I almost went out the door with scripts that are now broken due to this.
Was the breaking of backwards compatibility on purpose? It worked BEFORE 0.9.9

This isn't just when referencing the current location, but when specifying ANY source.

[thigg]

I think this was not intentional, as far as I understand this is just the way Windows deals with cmd inputs. It seems to be different if the target is a posh-script

[ferventcoder]

@ryanroundhouse this is a breaking change, not necessarily intentional. What did you have before? We can attempt to bring about something that will allow this to work with new choco.

[ferventcoder]

The problem here is we removed a bunch of layers. Before it was shim -> cmd -> powershell (jumping through hoops to ensure quotes made it all the way down). Now it is just shim -> exe.

[ghost]

I was using the same thing as thigg. The documentation he linked to suggested using apostrophes around paths (ie: 'c:\program files (x86)\path\to local\store;http://chocolatey.org/api/v2/').

It now complains that the package cannot be found and it is checking:
Source(s): "'c:\program"

[thigg]

Would be nice to be backward compatible, also for scripts which are using chocolatey.

[ferventcoder]

agreed. Adjusted. this should be 0.9.9.1

[thigg]

So it should allow "test" 'test' and '"test'" (single, double and combined)?

[ferventcoder]

Also keep in mind that we can only do so much here. There is a difference between how powershell handles and how cmd handles it.

[ferventcoder]

In some places we've already tried to cover that - powershell may have never handled single quotes.

[thigg]

But if the target is an exe file, we should be able to do the whole formatting as we like it, right?

[ferventcoder]

It should work as much the same way as before - I think the single tick marks apostrophes would may have only worked on cmd.exe - powershell would have stripped it right off.

[ghost]

I was using apostrophe, not a tick.

On Tue, Mar 3, 2015 at 1:49 PM, Rob Reynolds notifications@github.com
wrote:

It should work as much the same way as before - I think the single tick
marks would have only worked on cmd.exe - powershell would have stripped it
right off.

—
Reply to this email directly or view it on GitHub
#141 (comment).

[ferventcoder]

I was using apostrophe, not a tick.

Yeah sorry, I use those terms interchangeably (and technically incorrectly) meaning apostrophe. Backtick being something different.

[ferventcoder]

So chocolatey will properly handle apostrophes again.