Next: Development, Previous: Package Management, Up: Top [Contents][Index]
Guix and its package collection are updated by running guix pull
(see Invoking guix pull). By default guix pull downloads and
deploys Guix itself from the official GNU Guix repository. This can be
customized by defining channels in the
~/.config/guix/channels.scm file. A channel specifies a URL and branch
of a Git repository to be deployed, and guix pull can be instructed
to pull from one or more channels. In other words, channels can be used
to customize and to extend Guix, as we will see below.
Guix is able to take into account security concerns and deal with authenticated
updates.
| • Specifying Additional Channels | Extending the package collection. | |
| • Using a Custom Guix Channel | Using a customized Guix. | |
| • Replicating Guix | Running the exact same Guix. | |
| • Channel Authentication | How Guix verifies what it fetches. | |
| • Channels with Substitutes | Using channels with available substitutes. | |
| • Creating a Channel | How to write your custom channel. | |
| • Package Modules in a Sub-directory | Specifying the channel’s package modules location. | |
| • Declaring Channel Dependencies | How to depend on other channels. | |
| • Specifying Channel Authorizations | Defining channel authors authorizations. | |
| • Primary URL | Distinguishing mirror to original. | |
| • Writing Channel News | Communicating information to channel’s users. |
Next: Development, Previous: Package Management, Up: Top [Contents][Index]