Skip to content

brogers5/chocolatey-package-foxitreader

Repository files navigation

Chocolatey Package: Foxit PDF Reader

Chocolatey package version Chocolatey package download count

Install

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

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

Alternatively, the packages as published on the Chocolatey Community Repository (starting with v11.0.0.49893) 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 foxitreader --source="'.;https://community.chocolatey.org/api/v2/'"

Build

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

choco pack

A successful build will create foxitreader.w.x.y.z.nupkg, where w.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.

Update

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 (foxitreader). Your local repository should therefore be cloned accordingly:

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

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

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

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 or package is available), pass the -Force switch:

.\update.ps1 -Force

Note

The update script stores the last ETag value served with the download, in order to detect possible silent updates (which would require a new package to update the installer's checksum). If a new value is detected, package updates will be forced, even if -Force was not passed.

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