Chocolatey Package: LocalSend
This package is part of a family of packages published for LocalSend. This repository is for the meta package.
- For the installer package, see chocolatey-package-localsend.install.
- For the portable package, see chocolatey-package-localsend.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 stable version from the Chocolatey Community Repository:
choco install localsend --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 localsend --source="'.;https://community.chocolatey.org/api/v2/'"
Install Chocolatey, clone this repository, and run the following command in the cloned repository:
choco pack
A successful build will create localsend.x.y.z.nupkg
, where x.y.z
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 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 (localsend
). Your local repository should therefore be cloned accordingly:
git clone [email protected]:brogers5/chocolatey-package-localsend.git localsend
Alternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the AU packages template):
mklink /J localsend ..\chocolatey-package-localsend
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.
To forcibly create an updated package (regardless of whether a new software version is available), pass the -Force
switch:
.\update.ps1 -Force
Before submitting a pull request, please test the package using the Chocolatey Testing Environment first.