Ecosyste.ms: Awesome

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

Awesome Lists | Featured Topics | Projects

https://github.com/pilskalns/choco-au-packages

Chocolatey Automatic Package Updater Module
https://github.com/pilskalns/choco-au-packages

Last synced: 2 days ago
JSON representation

Chocolatey Automatic Package Updater Module

Awesome Lists containing this project

README 

        



[![](https://ci.appveyor.com/api/projects/status/github/Pilskalns/choco-au-packages?svg=true)](https://ci.appveyor.com/project/Pilskalns/choco-au-packages)

[Update status](https://gist.github.com/Pilskalns/1b0f0584554f6e98b14aca7f2fec2230)

[![](http://transparent-favicon.info/favicon.ico)](#)

[chocolatey/pilskalns](https://chocolatey.org/profiles/pilskalns)



This repository contains [chocolatey automatic packages](https://chocolatey.org/docs/automatic-packages).

The repository is setup so that you can manage your packages entirely from the GitHub web interface (using AppVeyor to update and push packages) and/or using the local repository copy.



## Prerequisites



To run locally you will need:



- Powershell 5+.

- [Chocolatey Automatic Package Updater Module](https://github.com/majkinetor/au): `Install-Module au` or `cinst au`.



In order to setup AppVeyor update runner please take a look at the AU wiki [AppVeyor section](https://github.com/majkinetor/au/wiki/AppVeyor).



## Create a package



To create a new package see [Creating the package updater script](https://github.com/majkinetor/au#creating-the-package-updater-script).



## Testing the package



In a package directory run: `Test-Package`. This function can be used to start testing in [chocolatey-test-environment](https://github.com/majkinetor/chocolatey-test-environment) via `Vagrant` parameter or it can test packages locally.



## Automatic package update



### Single package



Run from within the directory of the package to update that package:



    cd 

    ./update.ps1



If this script is missing, the package is not automatic.

Set `$au_Force = $true` prior to script call to update the package even if no new version is found.



### Multiple packages



To update all packages run `./update_all.ps1`. It accepts few options:



```powershell

./update_all.ps1 -Name a*                         # Update all packages which name start with letter 'a'

./update_all.ps1 -ForcedPackages 'cpu-z copyq'    # Update all packages and force cpu-z and copyq

./update_all.ps1 -ForcedPackages 'copyq:1.2.3'    # Update all packages but force copyq with explicit version

./update_all.ps1 -Root 'c:\packages'              # Update all packages in the c:\packages folder

```



The following global variables influence the execution of `update_all.ps1` script if set prior to the call:



```powershell

$au_NoPlugins = $true        #Do not execute plugins

$au_Push      = $false       #Do not push to chocolatey

```



You can also call AU method `Update-AUPackages` (alias `updateall`) on its own in the repository root. This will just run the updater for the each package without any other option from `update_all.ps1` script. For example to force update of all packages with a single command execute:



    updateall -Options ([ordered]@{ Force = $true })



## Testing all packages



You can force the update of all or subset of packages to see how they behave when complete update procedure is done:



```powershell

./test_all.ps1                            # Test force update on all packages

./test_all.ps1 'cdrtfe','freecad', 'p*'   # Test force update on only given packages

./test_all.ps1 'random 3'                 # Split packages in 3 groups and randomly select and test 1 of those each time

```



**Note**: If you run this locally your packages will get updated. Use `git reset --hard` after running this to revert the changes.



## Pushing To Community Repository Via Commit Message



You can force package update and push using git commit message. AppVeyor build is set up to pass arguments from the commit message to the `./update_all.ps1` script.



If commit message includes `[AU ]` message on the first line, the `forced_packages` string will be sent to the updater.



Examples:

- `[AU pkg1 pkg2]`

Force update ONLY packages `pkg1` and `pkg2`.

- `[AU pkg1:ver1 pkg2 non_existent]`

Force `pkg1` and use explicit version `ver1`, force `pkg2` and ignore `non_existent`.



To see how versions behave when package update is forced see the [force documentation](https://github.com/majkinetor/au/blob/master/README.md#force-update).



You can also push manual packages with command `[PUSH pkg1 ... pkgN]`. This works for any package anywhere in the file hierarchy and will not invoke AU updater at all.



If there are no changes in the repository use `--allow-empty` git parameter:



    git commit -m '[AU copyq less:2.0]' --allow-empty

    git push



## Start using AU with your own packages



To use this system with your own packages do the following steps:



* Fork this project. If needed, rename it to `au-packages`.

* Delete all existing packages.

* Edit the `README.md` header with your repository info.

* Set your environment variables. See [AU wiki](https://github.com/majkinetor/au/wiki#environment-variables) for details.



Add your own packages now, with this in mind:

* You can keep both manual and automatic packages together. To get only AU packages any time use `Get-AUPackages` function (alias `lsau` or `gau`)

* Keep all package additional files in the package directory (icons, screenshots etc.). This keeps everything related to one package in its own directory so it is easy to move it around or remove it.