Chocolatey - the package manager for Windows
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
You can just call me choco.
Come join in the conversation about Chocolatey in our Gitter Chat Room.
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.
Chocolatey FOSS install showing tab completion and
(a way to update environment variables without restarting your shell):
Chocolatey Pro showing private CDN download cache and virus scan protection:
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.
Please see the docs
a shot (or
). For specific commands, add the command and then the help switch e.g.
choco.exe install -h
Observe the following help for submitting an issue:
Submitting a ticket:
. 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).
) 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.
If you would like to contribute code or help squash a bug or two, that's awesome. Please familiarize yourself with CONTRIBUTING.
Committers, you should be very familiar with COMMITTERS.
There is a
file that creates a necessary generated file named
. It must be run at least once before Visual Studio will build.
file to help with code conventions).
Running the build on Windows should produce an artifact that is tested and ready to be used.
# install prerequisites sudo apt install apt-transport-https dirmngr gnupg ca-certificates # add the key sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF # add the package repository # Debian 10 echo "deb https://download.mono-project.com/repo/debian stable-buster main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list # Debian 9 echo "deb https://download.mono-project.com/repo/debian stable-stretch main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list # Ubuntu 18.04 echo "deb https://download.mono-project.com/repo/ubuntu stable-bionic main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list # Ubuntu 16.04 echo "deb https://download.mono-project.com/repo/ubuntu stable-xenial main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list # update package indexes sudo apt-get update # install sudo apt-get install mono-devel -y
### NOT FULLY TESTED AND WORKING ### # Switch to root shell su # Add the EPEL yum install epel-release -y # Add the key pmkeys --import "http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x3fa7e0328081bff6a14da29aa6a19b38d3d831ef" # Add the package repository # CentOS/RHEL 8 su -c 'curl https://download.mono-project.com/repo/centos8-stable.repo | tee /etc/yum.repos.d/mono-centos8-stable.repo' # CentOS/RHEL 7 su -c 'curl https://download.mono-project.com/repo/centos7-stable.repo | tee /etc/yum.repos.d/mono-centos7-stable.repo' # CentOS/RHEL 6 rpm --import "http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x3fa7e0328081bff6a14da29aa6a19b38d3d831ef" # Update your system yum update -y # Install mono-devel yum install mono-devel -y
### NOT FULLY TESTED AND WORKING ### # Switch to root shell su # Add the key rpm --import "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF" # Add the package repository # Fedora 29 su -c 'curl https://download.mono-project.com/repo/centos8-stable.repo | tee /etc/yum.repos.d/mono-centos8-stable.repo' # Fedora 28 su -c 'curl https://download.mono-project.com/repo/centos7-stable.repo | tee /etc/yum.repos.d/mono-centos7-stable.repo' # Update dnf update # Install mono-devel dnf install mono-devel -y
(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
chmod +x build.sh chmod +x zip.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.
Chocolatey is brought to you by quite a few people and frameworks. See CREDITS (just LEGAL/Credits.md in the zip folder).