A convenient way to use chocolatey is to make a 2 lines bat file where the first line just installs chocolatey (with the handy oneliner in your homepage), and the second line simply runs "choco install ", like so:
Then this would be a lightweight portable installer and updater for all those packages. Which is simple for people to understand, redistribute and use.
However, because the first line always downloads and install chocolatey this could cause problems (and also unnecessary bandwidth consumption). Bat files are a pain for handling conditional evaluation and check whether choco exists, and it wouldn't be straightforward anymore for the average user to complicate the script or to use powershell or any other different language.
So it would be nice if the install.ps1 that installs chocolatey for the first time was able to check first if chocolatey was already installed and working. And if so, simply call a proper "choco update".
A convenient way to use chocolatey is to make a 2 lines bat file where the first line just installs chocolatey (with the handy oneliner in your homepage), and the second line simply runs "choco install
", like so:
Then this would be a lightweight portable installer and updater for all those packages. Which is simple for people to understand, redistribute and use.
However, because the first line always downloads and install chocolatey this could cause problems (and also unnecessary bandwidth consumption). Bat files are a pain for handling conditional evaluation and check whether choco exists, and it wouldn't be straightforward anymore for the average user to complicate the script or to use powershell or any other different language.
So it would be nice if the install.ps1 that installs chocolatey for the first time was able to check first if chocolatey was already installed and working. And if so, simply call a proper "choco update".