From: Felix Bier <Felix.Bier@rohde-schwarz.com>
To: "gentoo-catalyst@lists.gentoo.org" <gentoo-catalyst@lists.gentoo.org>
Subject: Re: [Newsletter] Re: [gentoo-catalyst] Re: [PATCH] Documentation: Make existing multi-overlay support more explicit
Date: Tue, 10 Nov 2020 00:56:19 +0000 [thread overview]
Message-ID: <dc2d0d24541058f2d3a141e0c34746271d3d1353.camel@rohde-schwarz.com> (raw)
In-Reply-To: <CAEdQ38GpfNk-K6OG148G+xsZnVaMXYnLHYutmkEXD0n8+LOa0A@mail.gmail.com>
The code already supports multiple repositories. This commit adapts the
documentation to make this more explicit.
Signed-off-by: Felix Bier <felix.bier@rohde-schwarz.com>
---
doc/catalyst-spec.5.txt | 5 +++--
examples/generic_stage_template.spec | 5 +++--
examples/livecd-stage1_template.spec | 5 +++--
examples/livecd-stage2_template.spec | 5 +++--
examples/netboot_template.spec | 5 +++--
examples/stage4_template.spec | 5 +++--
6 files changed, 18 insertions(+), 12 deletions(-)
diff --git a/doc/catalyst-spec.5.txt b/doc/catalyst-spec.5.txt
index 31e69820..4c1df857 100644
--- a/doc/catalyst-spec.5.txt
+++ b/doc/catalyst-spec.5.txt
@@ -81,8 +81,9 @@ This is an optional directory containing portage configuration files
problems.
*portage_overlay*::
-This option specifies the location to a portage overlay that you would
-like to use when building this target (example: `/usr/local/portage`).
+This option specifies the location of the ebuild repositories that you would
+like to have used when building this target. It takes a space-separated list
+of directory names. (example: `/usr/local/portage`).
*pkgcache_path*::
This allows the optional directory containing the output packages for
diff --git a/examples/generic_stage_template.spec b/examples/generic_stage_template.spec
index 8f0375c4..8c8889bf 100644
--- a/examples/generic_stage_template.spec
+++ b/examples/generic_stage_template.spec
@@ -89,8 +89,9 @@ decompressor_search_order: lbzip2 bzip2 tar pixz xz gzip squashfs
# portage_confdir: /etc/portage
portage_confdir:
-# This option specifies the location to a portage overlay that you would like to
-# have used when building this target.
+# This option specifies the location of the ebuild repositories that you would
+# like to have used when building this target. It takes a space-separated list
+# of directory names.
# example:
# portage_overlay: /usr/local/portage
portage_overlay:
diff --git a/examples/livecd-stage1_template.spec b/examples/livecd-stage1_template.spec
index b921372a..269a1e3d 100644
--- a/examples/livecd-stage1_template.spec
+++ b/examples/livecd-stage1_template.spec
@@ -52,8 +52,9 @@ source_subpath:
# portage_confdir: /etc/portage
portage_confdir:
-# This option specifies the location to a portage overlay that you would like to
-# have used when building this target.
+# This option specifies the location of the ebuild repositories that you would
+# like to have used when building this target. It takes a space-separated list
+# of directory names.
# example:
# portage_overlay: /usr/local/portage
portage_overlay:
diff --git a/examples/livecd-stage2_template.spec b/examples/livecd-stage2_template.spec
index ac1cd3e4..4f50919f 100644
--- a/examples/livecd-stage2_template.spec
+++ b/examples/livecd-stage2_template.spec
@@ -52,8 +52,9 @@ source_subpath:
# portage_confdir: /etc/portage
portage_confdir:
-# This option specifies the location to a portage overlay that you would like to
-# have used when building this target.
+# This option specifies the location of the ebuild repositories that you would
+# like to have used when building this target. It takes a space-separated list
+# of directory names.
# example:
# portage_overlay: /usr/local/portage
portage_overlay:
diff --git a/examples/netboot_template.spec b/examples/netboot_template.spec
index 4f76b8ff..ad9d993c 100644
--- a/examples/netboot_template.spec
+++ b/examples/netboot_template.spec
@@ -6,8 +6,9 @@ profile: uclibc/mips
snapshot: 20060107
source_subpath: default/stage3-mips-uclibc-mips3-2006.126
-# This option specifies the location to a portage overlay that you would like to
-# have used when building this target.
+# This option specifies the location of the ebuild repositories that you would
+# like to have used when building this target. It takes a space-separated list
+# of directory names.
# example:
# portage_overlay: /usr/local/portage
portage_overlay:
diff --git a/examples/stage4_template.spec b/examples/stage4_template.spec
index c901eabc..aea70e86 100644
--- a/examples/stage4_template.spec
+++ b/examples/stage4_template.spec
@@ -52,8 +52,9 @@ source_subpath:
# portage_confdir: /etc/portage
portage_confdir:
-# This option specifies the location to a portage overlay that you would like to
-# have used when building this target.
+# This option specifies the location of the ebuild repositories that you would
+# like to have used when building this target. It takes a space-separated list
+# of directory names.
# example:
# portage_overlay: /usr/local/portage
portage_overlay:
--
2.29.2
prev parent reply other threads:[~2020-11-10 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 18:45 [gentoo-catalyst] [PATCH] Documentation: Make existing multi-overlay support more explicit Felix Bier
2020-10-18 15:07 ` [gentoo-catalyst] " Felix Bier
2020-10-30 15:54 ` Matt Turner
2020-11-10 0:51 ` [Newsletter] " Felix Bier
2020-11-10 0:56 ` Felix Bier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc2d0d24541058f2d3a141e0c34746271d3d1353.camel@rohde-schwarz.com \
--to=felix.bier@rohde-schwarz.com \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox