Chocolatey Package: ViVeTool

Install

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

choco install vivetool --source="'https://community.chocolatey.org/api/v2'"

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 (with dependencies sourced from the Community Repository) as follows:

choco install vivetool --source="'.;https://community.chocolatey.org/api/v2/'"

Build

Install Chocolatey, the Chocolatey Automatic Package Updater Module, and the PowerShellForGitHub PowerShell Module, then clone this repository.

Once cloned, simply run build.ps1. The ZIP archive is intentionally untracked to avoid bloating the repository, so the script will download the ViVeTool portable ZIP archive from the official distribution point, then packs everything together.

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

Note Chocolatey package builds are non-deterministic. Consequently, an independently built package's checksum will not match that of the officially published package.

Update

This package should be automatically updated by the Chocolatey Automatic Package Updater Module, with update queries implemented by the PowerShellForGitHub PowerShell Module. If it is outdated by more than a few days, please open an issue.

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

git clone git@github.com:brogers5/chocolatey-package-vivetool.git vivetool

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

mklink /J vivetool ..\chocolatey-package-vivetool

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 with a Windows 10 build 18963+ environment similar to the Chocolatey Testing Environment first.