Automatic and manual nuget-based packages for management by Chocolatey.

Chocolatey is a package manager like apt-get or yum; designed for a command-line interface for management and installing MSI, EXE, and portable user applications. Nuget is mainly designed for installing developer libraries.

Chocolatey package API ODATA feed

Presentation resources (read the Odata feed and presents it to you in various methods and formats)

• Web: Chocolatey.org
• App: ChocolateyGUI
• App: OuiGuiChocolatey
• Cmd: choco list -h

Chocolatey Wiki

Chocolatey Frequently Asked Questions (FAQ)

chocolatey-packages
├── automatic
│   ├── _output
│   │   ├── andy    
│   │   │   ├── 0.43.2    
│   │   │   │   ├── tools
│   │   │   │   │   ├── chocolateyInstall.ps1
│   │   │   │   │   └── chocolateyUninstall.ps1
│   │   │   │   ├── andy.0.43.2.nupkg
│   │   │   │   └── andy.nuspec    
│   │   │   └── 0.43.3  
│   │   └── bitcoin 
│   │   │   ...
│   │   └── zsnes
│   ├── andy
│   │   ├── tools
│   │   │   ├── chocolateyInstall.ps1
│   │   │   └── chocolateyUninstall.ps1
│   │   └── andy.nuspec
│   ├── bitcoin
│   │   ...
│   └── zsnes
├── icons
│   ├── andy.png
│   ├── bitcoin.svg
│   │   ...
│   └── zsnes.png
├── ketarin
│   ├── andy.xml
│   ├── bitcoin.xml
│   │   ...
│   └── zsnes.xml
├── licenses
└── manual
    └── hpusbdisk
        ├── tools
        │   ├── chocolateyInstall.ps1    
        │   └── HPUSBDisk.exe    
        ├── hpusbdisk.2.2.3.20150128.nupkg
        └── hpusbdisk.nuspec

Package manifest: Nuspec (nuspec)
Install and uninstall scripts: PowerShell (ps1)

GUI automation: AutoHotKey (ahk) or AutoIt (au3)

1. scraping HTTP with regular expressions using ketarin, then
2. populating a reserved layout to XML and powershell install/uninstall/setup scripts with chocopkgupdater or other scripts, and finally
3. packing the generated source files into a zip file, saved as a nupkg
4. pushing the nupkg file to chocolaty feed for moderation

Each sub-directory is equivalent to the application ID, otherwise known as the Application Name in Ketarin and stored in Ketarin's variable {appname}

See ketarin\README.md for more information about automatically updating packages from this repo.

Icons pointed to in the nuspec manifest file by XML tag <iconUrl>. These URLs are shown as the package graphic on Chocolatey.org for the respective package.

e.g. the icon on https://chocolatey.org/packages/gtk-runtime/2.24.10.20121010 is linked to https://cdn.rawgit.com/dtgm/chocolatey-packages/19d35dff574b7496b92f235fa1503d47b861871a/icons/gtk-runtime.svg and is configured in gtk-runtime.nuspec by XML tag <iconUrl> when nuget.exe push gtk-runtime.1.2.3.nupkg -Source https://chocolatey.org/ (performed without user intervention by chocolateypackageupdater).

The URL that should be used should not point directly to the file. Instead, use this service http://rawgit.com/

Limited use cases where the legal user agreements to terms of usage of the software for packages being installed is not available or not in reliably published way for Internet access.

If applicable, this location would be pointed to by <licenseUrl>.

However, most all packages point directly to the LICENSE or COPYING file if the source code is publicly available. Otherwise, the <licenseUrl> points to the licensing terms as published on a publicly available web page.

Packages that must have their nuspec and powershell control scripts manually edited (text editor), packaged (cpack) and pushed (cpush).

Only packages that never get updated should be here.

Note that while Nupkg files may contain any binary file, typically, they only contain essential wrapper information explaining where the install program is located and how to install the program. However, since packages in this folder may no longer have an official published source, they may be more likely to contain the executable or install file(s) directly within the zipped nupkg file.

• https://github.com/alanstevens/ChocoPackages
• https://github.com/AnthonyMastrean/chocolateypackages
• https://github.com/aronovgj/choco-auto
• https://github.com/chocolatey/chocolatey-coreteampackages
• https://github.com/ComFreek/chocolatey-packages
• https://github.com/ferventcoder/chocolatey-packages
• https://github.com/tunisiano187/Chocolatey-packages
• [Last update 2016] https://github.com/MarkRobertJohnson/ChocolateyPackages
• [Last update 2018] https://github.com/Redsandro/chocolatey
• [Last update 2016] https://github.com/yoshimov/chocolatey-packages
• [DEPRECATED 2018] https://github.com/adgellida/chocolateyautomaticpackages

• Chocolatey is cross-platform.
• Package managers are quite mature in Linux relative to Windows.

For ease of transition between OS', it is recommended to use the same ID as used in other package managers when possible.

• .apk — Android
• .appx, .appxbundle — used by Microsoft for packaging Windows 8, Windows 8.1, and Windows Phone 8.1 applications.[2]
• .deb — Used by Debian and its derivatives, such as Ubuntu, Xubuntu, and CrunchBang Linux.[3]
• ebuild — Used by Gentoo Linux.[4]
• PISI — Used by Pardus and derivatives such as Pardus-Anka and Pisi Linux.[citation needed]
• .pkg - Used by iPhone, PlayStation 3, Solaris (operating system).[citation needed]
• PUP and PET — used by Puppy Linux - click and install package type. OS can be installed to a flash drive for portability and will bring apps with it.[5]
• QPKG — Used by QNAP NAS devices.[6]
• .rpm — Used by Red Hat Enterprise Linux, Fedora, derivatives such as CentOS and SUSE Linux Enterprise Server.[7]
• SLP — Used by Stampede Linux.[citation needed]
• .pkg.tar.xz — Used by Arch Linux's Pacman package manager.[8]
• .tgz, .txz, .tbz, .tlz — Used by Slackware.[9]

• Debian: stable text list -- Ubuntu: http://packages.ubuntu.com/ (trusty text list)
• Redhat Fedora: https://admin.fedoraproject.org/pkgdb/ -- Others: http://rpm.pbone.net/, http://rpmfind.net/,
• Gentoo: categories, text list (also at MIRROR/pub/gentoo/distfiles/)
• Arch: repos, mirror text list

These packages are a community effort. Your help is appreciated!

If packages from this repository fail to install or a new version has been released by the software vendor for a particular package, please report it in any or all of the following ways:

Github issue: https://github.com/dtgm/chocolatey-packages/issues/new Disqus comment on the package's gallery page: https://chocolatey.org/packages/PKGID#discussion Send an email on the package's gallery page: https://chocolatey.org/packages/PKGID/ContactOwners

If the package fails to install or uninstall via choco, please include debug information from the console:
choco install PKGID --yes --verbose --debug

If the package is not up to date, please include the following if possible:

• latest version number
• release date
• URL to the install binary

This repository uses Git for management. If you don't know what Git is, or don't want to create a local copy of this repository, GitHub allows you to edit text files and publish back changes to this repository entirely from their website. For example, to fix a spelling error in this README.md file:

1. Sign up for a free GitHub account
   https://github.com/join
2. Fork this repository
   https://github.com/dtgm/chocolatey-packages
3. Make changes to your forked repository
   https://github.com/YOU/chocolatey-packages/edit/master/README.md
4. Commit (save) changes to your repository
   For absolute beginners, only make edits to a single file and commit to the master branch. Note that you can make multiple commits to any one or multiple files and they will all show up in the Pull request which is why you want to use branching. That way you group related changes together. For example, if you see a common spelling error in many files, you may want to change all those text files containing just that spelling error under a specific branch like "Spelling-error-01". Name your branch whatever makes sense to you that is related to the change you are making.
5. Create a new Pull Request (PR)
   https://github.com/YOU/chocolatey-packages/pulls

Note that GitHub also has its own text paste bin at https://gist.github.com/

For more help with using GitHub, see https://help.github.com/