Chocolatey Package: PS Remote Play
Install Chocolatey, and run the following command to install the latest approved stable version from the Chocolatey Community Repository:
choco install ps-remote-play --source="'https://community.chocolatey.org/api/v2'"Alternatively, the packages as published on the Chocolatey Community Repository (starting with v7.5.0.8061) 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 ps-remote-play --source="'.;https://community.chocolatey.org/api/v2/'"Install Chocolatey, clone this repository, and run the following command in the cloned repository:
choco packA successful build will create ps-remote-play.w.x.y.z.nupkg, where w.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.
This package should be automatically updated by the Chocolatey Automatic Package Updater 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 (ps-remote-play). Your local repository should therefore be cloned accordingly:
git clone [email protected]:brogers5/chocolatey-package-ps-remote-play.git ps-remote-playAlternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the AU packages template):
mklink /J ps-remote-play ..\chocolatey-package-ps-remote-playOnce 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 latest Chocolatey Testing Environment first.