[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
01/02: website: package-channel: Fix typos, follow suggestions.
From: |
Ludovic Courtès |
Subject: |
01/02: website: package-channel: Fix typos, follow suggestions. |
Date: |
Mon, 5 Jun 2023 05:26:54 -0400 (EDT) |
civodul pushed a commit to branch master
in repository guix-artwork.
commit 0eb014a4bded0b798e4863e8b88b5c6963a93a2a
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Mon Jun 5 10:00:35 2023 +0200
website: package-channel: Fix typos, follow suggestions.
Thanks to Attila and bjc on #guix.
* website/drafts/package-channel.md: Fix typos, follow suggestions.
---
website/drafts/package-channel.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/website/drafts/package-channel.md
b/website/drafts/package-channel.md
index aa42c05..2e45609 100644
--- a/website/drafts/package-channel.md
+++ b/website/drafts/package-channel.md
@@ -31,7 +31,7 @@ seen, will be to add a `guix.scm` at the root of the
repository we’re
interested in. We’ll take [Guile](https://www.gnu.org/software/guile)
as an example in this post: it’s written in Scheme (mostly) and C, and
has a number of dependencies—a C compilation tool chain, C libraries,
-Autoconf and its friends, LaTeX, and so on. The resulting `guix.scm` is
+Autoconf and its friends, LaTeX, and so on. The resulting `guix.scm`
looks like the usual [package
definition](https://guix.gnu.org/manual/en/html_node/Defining-Packages.html),
just without the `define-public` bit:
@@ -118,7 +118,7 @@ listed above, but also _implicit dependencies_ such as the
GCC tool
chain, GNU Make, sed, grep, and so on. The chef’s recommendation:
```
-guix shell -CP
+guix shell --container --link-profile
```
That gives a shell in an isolated container, and all the dependencies
@@ -224,9 +224,9 @@ and that’s exactly what we’re doing with our `guix.scm`.
Granted, our
Git repository is one package definition lost in a sea of code—in this
case, Guile—, but still.
-Turns out we can indeed turn into a channel, but with one caveat: we
+Turns out we can indeed turn it into a channel, but with one caveat: we
must create a separate directory for the `.scm` file(s) of our channel
-so that `guix pull` doesn’t end loading unrelated `.scm` files when
+so that `guix pull` doesn’t load unrelated `.scm` files when
someone pulls the channel—and in Guile, there are lots of them! So
we’ll start like this, keeping a top-level `guix.scm` symlink for the
sake of `guix shell`:
@@ -458,7 +458,7 @@ channels providing a number of *jobs*—one job per package
defined in
As for substitutes, they come for free! As an example, our `guile`
jobset being built on ci.guix.gnu.org, one automatically gets
-substitutes for it from ci.guix.gnu.org. It’s as simple as this.
+substitutes for it from ci.guix.gnu.org. It’s as simple as that.
# Bonus: Build manifest