Chocolatey - the package manager for Windows
ferventcoder Merge branch 'stable'
* stable:
  (maint) formatting
  (doc) update generated docs
  (doc) Add notes / examples for silentArguments
Latest commit d2c65ec Aug 11, 2018
Permalink
Failed to load latest commit information.
.build.custom (GH-1496) Allow the creation of NoResources build Feb 20, 2018
.build (build) fix mono build - part deux Mar 18, 2017
.github (doc) move choco to bottom Jun 7, 2018
.nuget adding solution Dec 13, 2013
docker (maint) Add ability to build a Docker image. Mar 10, 2017
docs (doc) update generated docs Aug 10, 2018
lib (maint) Add instructions for strong naming NuGet Feb 20, 2018
nuget (doc) update release notes for 0.10.11 May 4, 2018
src (maint) formatting Aug 10, 2018
.editorconfig (maint) legal and notices Dec 14, 2013
.gitignore (maint) Added .vs folder to .gitignore Feb 16, 2018
.travis.yml (maint) Specify mono version for Travis-CI Jul 30, 2015
.uppercut (version) 0.10.11 May 4, 2018
CHANGELOG.md (GH-1577) Add cinstm removal to CHANGELOG.md Jun 7, 2018
CHANGELOG_LICENSED.md (doc) update licensed CHANGELOG Mar 4, 2018
COMMITTERS.md (doc) fix order in merge process Jun 7, 2018
CONTRIBUTING.md Merge branch 'stable' Jul 9, 2017
GenerateDocs.ps1 (GH-1476) Ensure docs are for Get-PackageParameters Mar 23, 2018
LICENSE (maint) legal and notices Dec 14, 2013
NOTICE (maint) Add 2018 to copyright year Feb 23, 2018
README.md (doc) remove donate Jun 7, 2018
Scenarios.md (GH-1313) pack - allow passing arbitrary properties Aug 6, 2017
appveyor.yml (build) configure coveralls.io Feb 7, 2015
build.bat (doc) attempt to document scenarios every run Jun 1, 2015
build.debug.bat (build) option to build debug version May 15, 2017
build.sh (build) fix mono build - part deux Mar 18, 2017
chocolatey.snk adding solution Dec 13, 2013
documentscenarios.bat (doc) update scenarios Jun 1, 2015
setup.cmd (maint) bringing in chocolatey nuspec Dec 15, 2013
setup.ps1 (maint) bringing in chocolatey nuspec Dec 15, 2013
test.bat (build) test.bat not quiet, no results Feb 16, 2015
zip.bat (build) upgrade to uc v1.4.5 Jan 24, 2015
zip.sh (build) fix mono build - part deux Mar 18, 2017

README.md

Chocolatey - like yum or apt-get, but for Windows

You can just call me choco.

Chocolatey Logo

Project Stats

Build Status

TeamCity AppVeyor Travis
TeamCity Build Status AppVeyor Build Status Travis Build Status

Chat Room

Come join in the conversation about Chocolatey in our Gitter Chat Room.

Gitter

Or, you can find us in IRC at #chocolatey on freenode. IRC is not as often checked by committers, so it is recommended you stick to Gitter if you need more timely assistance.

Please make sure you've read over and agree with the etiquette regarding communication.

Support Chocolatey!

See Chocolatey In Action

Chocolatey FOSS install showing tab completion and refreshenv (a way to update environment variables without restarting your shell):

install

Chocolatey Pro showing private CDN download cache and virus scan protection:

install w/pro

Etiquette Regarding Communication

If you are an open source user requesting support, please remember that most folks in the Chocolatey community are volunteers that have lives outside of open source and are not paid to ensure things work for you, so please be considerate of others' time when you are asking for things. Many of us have families that also need time as well and only have so much time to give on a daily basis. A little consideration and patience can go a long way. After all, you are using a pretty good tool without cost. It may not be perfect (yet), and we know that.

If you are using a commercial edition of Chocolatey, you have different terms! Please see support.

Information

Documentation

Please see the docs

Give choco.exe -? a shot (or choco.exe -h). For specific commands, add the command and then the help switch e.g. choco.exe install -h.

Requirements

  • .NET Framework 4.0+
  • PowerShell 2.0+
  • Windows Server 2003+ / Windows 7+

License / Credits

Apache 2.0 - see LICENSE and NOTICE files.

Submitting Issues

submitting issues

  1. Start with Troubleshooting and the FAQ to see if your question or issue already has an answer.
  2. If not found or resolved, please follow one of the following avenues:
    • If you are a licensed customer, please see support. You can also log an issue to Licensed Issues and we will submit issues to all other places on your behalf. Another avenue is to use email support to have us submit tickets and other avenues on your behalf (allowing you to maintain privacy).
    • If it is an enhancement request or issue with the website (the community package repository aka https://chocolatey.org), please submit the issue to the Chocolatey.org repo.
    • If you have found an issue with the GUI (Chocolatey GUI) or you want to submit an enhancement, please see the ChocolateyGUI repository.
    • If you have found an issue with the client (choco.exe), you are in the right place. Keep reading below.

Observe the following help for submitting an issue:

Prerequisites:

  • The issue has to do with choco itself and is not a package or website issue.
  • Please check to see if your issue already exists with a quick search of the issues. Start with one relevant term and then add if you get too many results.
  • You are not submitting an "Enhancement". Enhancements should observe CONTRIBUTING guidelines.
  • You are not submitting a question - questions are better served as emails or gitter chat questions.
  • Please make sure you've read over and agree with the etiquette regarding communication.

Submitting a ticket:

  • We'll need debug and verbose output, so please run and capture the log with -dv or --debug --verbose. You can submit that with the issue or create a gist and link it.
  • Please note that the debug/verbose output for some commands may have sensitive data (passwords or apiKeys) related to Chocolatey, so please remove those if they are there prior to submitting the issue.
  • choco.exe logs to a file in $env:ChocolateyInstall\log\. You can grab the specific log output from there so you don't have to capture or redirect screen output. Please limit the amount included to just the command run (the log is appended to with every command).
  • Please save the log output in a gist (save the file as log.sh) and link to the gist from the issue. Feel free to create it as secret so it doesn't fill up against your public gists. Anyone with a direct link can still get to secret gists. If you accidentally include secret information in your gist, please delete it and create a new one (gist history can be seen by anyone) and update the link in the ticket (issue history is not retained except by email - deleting the gist ensures that no one can get to it). Using gists this way also keeps accidental secrets from being shared in the ticket in the first place as well.
  • We'll need the entire log output from the run, so please don't limit it down to areas you feel are relevant. You may miss some important details we'll need to know. This will help expedite issue triage.
  • It's helpful to include the version of choco, the version of the OS, and the version of PowerShell (Posh) - the debug script should capture all of those pieces of information.
  • Include screenshots and/or animated gifs whenever possible, they help show us exactly what the problem is.

Contributing

If you would like to contribute code or help squash a bug or two, that's awesome. Please familiarize yourself with CONTRIBUTING.

Committers

Committers, you should be very familiar with COMMITTERS.

Compiling / Building Source

There is a build.bat/build.sh file that creates a necessary generated file named SolutionVersion.cs. It must be run at least once before Visual Studio will build.

Windows

Prerequisites:

  • .NET Framework 4+
  • Visual Studio is helpful for working on source.
  • ReSharper is immensely helpful (and there is a .sln.DotSettings file to help with code conventions).

Build Process:

  • Run build.bat.

Running the build on Windows should produce an artifact that is tested and ready to be used.

Other Platforms

Prerequisites:
  • Install and configure Mono 3.12.0 (3.8.0 should also work).
  • Debian based
# add the key

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
# add the package repository
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
# Ubuntu 12.10/12.04 - add this deb as well
echo "deb http://download.mono-project.com/repo/debian wheezy-libtiff-compat main" | sudo tee -a /etc/apt/sources.list.d/mono-xamarin.list

# update package indexes
sudo apt-get update
# install
sudo apt-get install mono-devel -y
### NOT FULLY TESTED AND WORKING ###
# add the EPEL
sudo yum install epel-release -y
# Add the key
sudo rpm --import "http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF"

# Add the package repository
sudo yum-config-manager --add-repo http://download.mono-project.com/repo/centos/

# update your system
sudo yum update -y

# Install mono-devel
sudo yum install mono-devel -y

  • Xamarin Studio is helpful for working on source.
  • Consider adding the following to your ~/.profile (or other relevant dot source file):
# mono
# http://www.michaelruck.de/2010/03/solving-pkg-config-and-mono-35-profile.html
# http://cloudgen.wordpress.com/2013/03/06/configure-nant-to-run-under-mono-3-06-beta-for-mac-osx/
export PKG_CONFIG_PATH=/opt/local/lib/pkgconfig:/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig:$PKG_CONFIG_PATH
  • Set your permissions correctly:
chmod +x build.sh
chmod +x zip.sh
Build Process:
  • Run ./build.sh.

Running the build on Mono produces an artifact similar to Windows but may have more rough edges. You may get a failure or two in the build script that can be safely ignored.

Credits

Chocolatey is brought to you by quite a few people and frameworks. See CREDITS (just LEGAL/Credits.md in the zip folder).