Ecosyste.ms: Awesome

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

Awesome Lists | Featured Topics | Projects

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

Chocolatey package for RWEverything (meta package).
https://github.com/brogers5/chocolatey-package-rweverything

au au-packages chocolatey chocolatey-automatic chocolatey-packages package packaging powershell powershell-script powershell-scripting rweverything software software-management windows

Last synced: about 4 hours ago
JSON representation

Chocolatey package for RWEverything (meta package).

Awesome Lists containing this project

README 

        
#  Chocolatey Package: [RWEverything](https://community.chocolatey.org/packages/rweverything/)



[![Chocolatey package version](https://img.shields.io/chocolatey/v/rweverything.svg)](https://community.chocolatey.org/packages/rweverything/)

[![Chocolatey package download count](https://img.shields.io/chocolatey/dt/rweverything.svg)](https://community.chocolatey.org/packages/rweverything/)



---



This package is part of a family of packages published for RWEverything. This repository is for the meta package.



* For the installer package, see [chocolatey-package-rweverything.install](https://github.com/brogers5/chocolatey-package-rweverything.install).

* For the portable package, see [chocolatey-package-rweverything.portable](https://github.com/brogers5/chocolatey-package-rweverything.portable).



See the [Chocolatey FAQs](https://docs.chocolatey.org/en-us/faqs) for more information on [meta packages](https://docs.chocolatey.org/en-us/faqs#what-is-the-difference-between-packages-no-suffix-as-compared-to.install.portable) and [installer/portable packages](https://docs.chocolatey.org/en-us/faqs#what-distinction-does-chocolatey-make-between-an-installable-and-a-portable-application).



---



## Install



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



```shell

choco install rweverything

```



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



```shell

choco install rweverything -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 `rweverything.x.y.nupkg`, where `x.y` 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 has an update script implemented with the [Chocolatey Automatic Package Updater Module](https://github.com/majkinetor/au), but the project does not appear to be actively maintained anymore, so it is not included with my normally scheduled update runs. If the project has a new release, please [open an issue](https://github.com/brogers5/chocolatey-package-rweverything/issues).



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



```shell

git clone [email protected]:brogers5/chocolatey-package-rweverything.git rweverything

```



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 rweverything ..\chocolatey-package-rweverything

```



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.



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 [Chocolatey Testing Environment](https://github.com/chocolatey-community/chocolatey-test-environment) first.