Get that Linux feeling - on Windows
Installing and Updating Cygwin Packages
Installing and Updating Cygwin for 64-bit versions of Windows
Signing key transition
The key used to sign setup binaries has been updated. During the transition period, signatures are made using both old (676041BA) and new (1A698DE9E2E56300) public keys here.
See this mail for more details.
General installation notes
When installing packages for the first time, the setup program does not install every package. Only the minimal base packages from the Cygwin distribution are installed by default, which takes up about 100 MB.
Clicking on categories and packages in the setup program package installation screen allows you to select what is installed or updated.
Individual packages like bash, gcc, less, etc. are released independently of the Cygwin DLL, so the Cygwin DLL version is not useful as a general Cygwin release number. The setup program tracks the versions of all installed components and provides the mechanism for installing or updating everything available from this site for Cygwin.
Once you've installed your desired subset of the Cygwin distribution, the setup program will remember what you selected, so re-running it will update your system with any new package releases.
On Windows Vista and later, the setup program will check by
default if it runs with administrative privileges and, if not, will try
to elevate the process. If you want to avoid this behaviour and install
under an unprivileged account just for your own usage, run
setup with the
Q: How do I add a package to my existing Cygwin installation?
A: Run the setup program and select the package you want to add.
Tip: if you don't want to also upgrade existing packages, select 'Keep' at the top-right of the package chooser page.
Q: Is there a command-line installer?
A: Yes and no. The setup program understands
arguments which allow you to control its behavior and choose
individual packages to install. While this provides some functionality
similar to such tools as
yum it is not as
full-featured as those package managers.
Q: Why not use
favourite package manager, etc.?
A: The basic reason for not using a more full-featured package manager is that such a program would need full access to all of Cygwin's POSIX functionality. That is, however, difficult to provide in a Cygwin-free environment, such as exists on first installation. Additionally, Windows does not easily allow overwriting of in-use executables so installing a new version of the Cygwin DLL while a package manager is using the DLL is problematic.
Q: How do I install everything?
A: You do not want to do this! This will install an enormous number of packages that you will never use, including debuginfo and source for every package.
If you really must do this, clicking on the "Default" label next to the "All" category to change it to "Install" will mark every Cygwin package for installation. Be advised that this will download and install tens of gigabytes of files to your computer.
Q: How do I verify the signature of setup?
$ gpg --recv-key 1A698DE9E2E56300 gpg: requesting key 1A698DE9E2E56300 from hkp server keys.gnupg.net gpg: key 1A698DE9E2E56300: "Cygwin <email@example.com>" imported gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model gpg: depth: 0 valid: 8 signed: 2 trust: 0-, 0q, 0n, 0m, 0f, 8u gpg: depth: 1 valid: 2 signed: 0 trust: 2-, 0q, 0n, 0m, 0f, 0u gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) $ gpg --keyid-format=long --with-fingerprint --verify setup-x86_64.exe.sig setup-x86_64.exe gpg: Signature made 12 Mar 2020 16:26:58 GMT gpg: using DSA key A9A262FF676041BA gpg: Good signature from "Cygwin <firstname.lastname@example.org>" Primary key fingerprint: 1169 DF9F 2273 4F74 3AA5 9232 A9A2 62FF 6760 41BA gpg: Signature made 12 Mar 2020 16:26:58 GMT gpg: using RSA key 1A698DE9E2E56300 gpg: Good signature from "Cygwin <email@example.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 5640 5CF6 FCC8 1574 682A 5D56 1A69 8DE9 E2E5 6300
Q: What's the hash of setup?
A: See here
Q: How do I help improve setup?
A: See the setup project page for more information.