Version, and create Chocolatey package of, the Chocolatey install script about home HOT 4 OPEN

I would recommend also having a package parameter to copy the script to a path on the local machine.

I'm unsure how we could best have a repository-solution agnostic upload without calling Chocolatey within the script, but it'll be a fun problem!

from home.

Since the Chocolatey installation script is a standalone artifact on the website, we might want to look into adding a version number, or perhaps a date/time, to the top of the file, so that there is a clear indication on the file itself about what version it is.

Thoughts?

from home.

At this point I'm starting to feel like we should chuck it in it's own repository (a public one, at that) so we can version it nicely and bring it into the website in another fashion.

from home.

Since the Chocolatey installation script is a standalone artifact on the website, we might want to look into adding a version number, or perhaps a date/time, to the top of the file, so that there is a clear indication on the file itself about what version it is.

Yeah, that makes sense.

from home.