This package is part of a family of packages published for RWEverything. This repository is for the installer package.

• For the meta package, see chocolatey-package-rweverything.
• For the portable package, see chocolatey-package-rweverything.portable.

See the Chocolatey FAQs for more information on meta packages and installer/portable packages.

Install Chocolatey, and run the following command to install the latest approved version on the Chocolatey Community Repository:

choco install rweverything.install

Alternatively, the packages as published on the Chocolatey Community Repository will also be mirrored on this repository's Releases page. The nupkg can be installed from the current directory as follows:

choco install rweverything.install -s .

Install Chocolatey, clone this repository, and run the following command in the cloned repository:

choco pack

A successful build will create rweverything.install.x.y.nupkg, where x.y should be the Nuspec's version value at build time.

Note that Chocolatey package builds are non-deterministic. Consequently, an independently built package will fail a checksum validation against officially published packages.

This package has an update script implemented with the Chocolatey Automatic Package Updater Module, but the project does not appear to be actively maintained anymore, so it is not included with my normally scheduled update runs. If the project has a new release, please open an issue.

AU expects the parent directory that contains this repository to share a name with the Nuspec (rweverything.install). Your local repository should therefore be cloned accordingly:

git clone [email protected]:brogers5/chocolatey-package-rweverything.install.git rweverything.install

Alternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the AU packages template):

mklink /J rweverything.install ..\chocolatey-package-rweverything.install

Once created, simply run update.ps1 from within the created directory/junction point. Assuming all goes well, all relevant files should change to reflect the latest version available. This will also build a new package version using the modified files.

Before submitting a pull request, please test the package using the Chocolatey Testing Environment first.