An open API service indexing awesome lists of open source software.

https://github.com/brogers5/chocolatey-package-imazing

Chocolatey package for iMazing.
https://github.com/brogers5/chocolatey-package-imazing

au au-packages backup chocolatey chocolatey-automatic chocolatey-packages imazing ios ipad iphone package packaging powershell powershell-script powershell-scripting software software-management sync windows

Last synced: about 1 month ago
JSON representation

Chocolatey package for iMazing.

Awesome Lists containing this project

README

          

# Chocolatey Package: [iMazing](https://community.chocolatey.org/packages/imazing)

[![Latest package version shield](https://img.shields.io/chocolatey/v/imazing.svg)](https://community.chocolatey.org/packages/imazing)
[![Total package download count shield](https://img.shields.io/chocolatey/dt/imazing.svg)](https://community.chocolatey.org/packages/imazing)

## Install

[Install Chocolatey](https://chocolatey.org/install), and run the following command to install the latest approved stable version from the Chocolatey Community Repository:

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

Alternatively, the packages as published on the Chocolatey Community Repository (starting with v2.18.1) will also be mirrored on this repository's [Releases page](https://github.com/brogers5/chocolatey-package-imazing/releases). The `nupkg` can be installed from the current directory (with dependencies sourced from the Community Repository) as follows:

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

## Build

[Install Chocolatey](https://chocolatey.org/install), clone this repository, and run the following command in the cloned repository:

```shell
choco pack
```

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

>[!Note]
>DigiDNA typically uses a 3-part version number for non-patch releases. Occasionally, they will create a patch release with four-part version numbers instead, so the filename pattern should be expected to change accordingly.

>[!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](https://github.com/majkinetor/au). If it is outdated by more than a few days, please [open an issue](https://github.com/brogers5/chocolatey-package-imazing/issues).

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

```shell
git clone git@github.com:brogers5/chocolatey-package-imazing.git imazing
```

Alternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the [AU packages template](https://github.com/majkinetor/au-packages-template)):

```shell
mklink /J imazing ..\chocolatey-package-imazing
```

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 limit the scope of update checks to a specific update channel, pass the `-IncludeStream` parameter with the desired Stream name:

```powershell
.\update.ps1 -IncludeStream 'V3'
```

```powershell
.\update.ps1 -IncludeStream 'V2'
```

To forcibly create an updated package (regardless of whether a new software version or package is available), pass the `-Force` switch:

```powershell
.\update.ps1 -Force
```

Before submitting a pull request, please [test the package](https://docs.chocolatey.org/en-us/community-repository/moderation/package-verifier#steps-for-each-package) using the latest [Chocolatey Testing Environment](https://github.com/chocolatey-community/chocolatey-test-environment) first.