Proposal: add scripts to the Chocolatey Community Package Repository

[aetonsi]

Hello,
first of all, THANK YOU for this wonderful collection of scripts.
I'd like to ask you, would it be possible and would you consider adding this collection of scripts to the choco repository?
With a scripts that adds the <installation folder>\Scripts subfolder to the environment path (like the installer of GOW does), it would be perfect!

Thank you for your time
Have a wonderful day
Andrea Edin

[fleschutz]

Hi Andrea,

Hello, first of all, THANK YOU for this wonderful collection of scripts. I'd like to ask you, would it be possible and would you consider adding this collection of scripts to the |choco| repository? With a scripts that adds the |<installation folder>\Scripts| subfolder to the environment path (like the installer of GOW <https://community.chocolatey.org/packages/Gow> does), it would be perfect!

Sure, why not? Any help from your side (e.g. step-by-step instructions or a pull request) would be very helpful and would also speed up things. Best regards, MarkusMessage ID: ***@***.***

[aetonsi]

Hello,
actually i have never created a choco package, sorry. I am simply an end user.

This is the official guide: https://docs.chocolatey.org/en-us/create/create-packages

If i understand correctly you have to setup a .nupkg package, and in that package you have an install script. This is what GOW does in its nupkg package:

You can download the .nupkg file by clicking Download in the left column (but please note: that is not the way you install a chocolatey package, you would simply use the command line choco install gow).
Anyway as you can see in their {Gow.0.8.0.nupkg}\tools\chocolateyInstall.ps1 they invoke the internal powershell function Install-ChocolateyPackage by passing the URL to GOW's installer on github, which is an .exe. That's it. The installer gets downloaded and executed, and it silently installs GOW, it takes care of everything. Theoretically You could create a release which includes an executable installer and do the same thing as them.

In any case you would have a whole nother problem: since your scripts are .ps1 files, you have to find a way to make them executable from any location in the system. Now that i think about it i'm not even sure if that's possible, considering that the shell can directly execute only files with extensions present in $env:PATHEXT (on my pc PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW;.CPL).

Just to be sure, I tried making placing a .ps1 file in a folder in the path and in a folder in $env:PSModulePath, but i was not able to execute my test script asd.ps1. Maybe you know how to do such a thing... here's what i tried:

Considerations:

• GOW works out of the box, simply by adding the GOW installation folder to $env:path, because they have .exes instead of .ps1s!
• If i'm not mistaken, i know that where only finds executable files (with extension in PATHEXT). that's why c:\tools\php54\asd.ps1 wasn't listed even though that folder is in the system path
• i tried using $env:PSModulePath as if it behaves like $env:path , but if i remember correctly powershell simply imports modules (eg. .psm1 files) from those folders
• a possible solution would be to create executables for each .ps1 script and have them automatically shimmed by the chocolatey package installer (see https://docs.chocolatey.org/en-us/create/create-packages#self-contained). This wouldn't be a smart solution IMO...

All of this considered, i don't know if my request is feasible... mainly because i don't know if it's possible to invoke the .ps1 scripts from other locations.