Next: Packages with Multiple Outputs, Previous: Invoking guix package, Up: Package Management [Contents][Index]
Guix supports transparent source/binary deployment, which means that it can either build things locally, or download pre-built items from a server, or both. We call these pre-built items substitutes—they are substitutes for local build results. In many cases, downloading a substitute is much faster than building things locally.
Substitutes can be anything resulting from a derivation build (see Derivations). Of course, in the common case, they are pre-built package binaries, but source tarballs, for instance, which also result from derivation builds, can be available as substitutes.
• Official Substitute Servers | One particular source of substitutes. | |
• Substitute Server Authorization | How to enable or disable substitutes. | |
• Getting Substitutes from Other Servers | Substitute diversity. | |
• Substitute Authentication | How Guix verifies substitutes. | |
• Proxy Settings | How to get substitutes via proxy. | |
• Substitution Failure | What happens when substitution fails. | |
• On Trusting Binaries | How can you trust that binary blob? |