search

chocolatey / home

The place to start for issues with areas of Chocolatey that are infrastructure related, or really any issues could be started here. There is also choco for the CLI client, Chocolatey GUI for the GUI.
Apache License 2.0
29 stars 10 forks source link

Version, and create Chocolatey package of, the Chocolatey install script #277

Open pauby opened 1 year ago

pauby commented 1 year ago

Checklist

Is Your Feature Request Related To A Problem? Please describe.

No response

Describe The Solution. Why is it needed?

Some feedback received after publishing the recent blog post about the changes made to Chocolatey CLI, it became clear that some organizations are using an outdated version of the installation script. Any new changes made to this script will not be propagated to their environments.

As we don't have a list of people / organizations that internalize that script, we cannot ensure that they get the latest version. If we create a Chocolatey package of the script, published to the Chocolatey Community Repository, then they can simply manage it in the normal way. As part of the Chocolatey package install script, we could provide package parameters that will allow the script to push the Chocolatey install script file to their internal repository.

Just to be clear, I understand that this is a chicken and egg scenario. How can you install the Chocolatey package without Chocolatey CLI? This change is intended for organizations that are internalizing the script and therefore have a least one working admin workstation.

Additional Context

This could also be used for Quick Start Guide and Chocolatey For Business Azure Environment.

Related Issues

No response

┆Issue is synchronized with this Gitlab issue by Unito

JPRuskin commented 1 year ago

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!

gep13 commented 1 year ago

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?

JPRuskin commented 1 year ago

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.

pauby commented 1 year ago

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.