(curl) Doesn't install using PowerShell Core as the host about chocolatey-packages HOT 6 OPEN

@PietJankbal Chocolatey CLI uses Windows PowerShell as it's host. Your 'Steps To Reproduce' don't provide enough information to reproduce the problem.

Running it here using Chocolaety CLI 2.2.2 I get the following:

My first suggestion is that you are using an unsupported open-source version of Chocolatey CLI and that you upgrade to 2.2.2 and try it again. If that doesn't work please go back to your first comment and edit it to provide all of the information rquired in 'Steps To Reproduce' and 'Environment'.

from chocolatey-packages.

Hi, I forgot to mention that I disabled the builtin powershell host. So first I ran:

choco.exe feature disable --name=powershellHost

from chocolatey-packages.

Chocolatey packages are only tested for working on Windows PowerShell.

If you want to submit a PR to update the package to allow it to work on both Windows PowerShell and PowerShell Core, then we could look at that. If not, I don't think this will get any traction and will automatically close.

from chocolatey-packages.

Well ok, then I think i will close this myself.
Nevertheless I would like to point out that I also opened a bugreport at PS Core, and they said to be careful using wildcards in Move-Item, and the difference in behaviour between PS Core and Windows PowerShell will not be fixed because of sane reasons.

See PowerShell/PowerShell#20521 (comment)

So maybe something to consider when writing new scripts.

from chocolatey-packages.

@PietJankbal The scenario that you are using (using PowerShell Core host with Chocolatey CLI scripts) isn't one that is common (I've never heard of it before). So this isn't an issue that the vast majority of people will run into.

Chocolatey CLI uses a Windows PowerShell host to run Chocolatey CLI scripts. Chocolatey CLI doesn't support PowerShell Core because it doesn't have to. Every Windows computer comes with Windows PowerShell.

Just to be clear on this repository. It is a community maintained repository, so when things need fixing / updating / changing, the expectation is that you submit those changes as a PR in the first instance.

Because the vast majority of people are never going to see this issue, I am guessing the community maintainers of this repository are unlikely to want to spend time fixing it.

Hopefully, that gives some context as to why the above comments were made.

from chocolatey-packages.