From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/1] docs: Fix typo in arch=all provides suffix
Date: Thu, 30 Jul 2026 09:38:05 +0200 [thread overview]
Message-ID: <20260730073805.396068-1-felix.moessbauer@siemens.com> (raw)
The suffix added to architecture-all providers is -archall, not -all.
The bigger example already had this correct, but the text missed it.
No functional change.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
RECIPE-API-CHANGELOG.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index f5b84c84..222e6fae 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -1083,7 +1083,7 @@ work for packages that generate both arch specific and arch all binary packages.
We now explicitly disable building `arch=all` binary packages during cross
compilation (this only affects packages that produce both architecture-specific
and `arch=all` binary packages). Recipes for such mixed packages should append
-`-all` to the `arch=all` binary packages listed in `PROVIDES` (e.g.,
+`-archall` to the `arch=all` binary packages listed in `PROVIDES` (e.g.,
`PROVIDES="foo-doc-archall"` for an `arch=all` binary package `foo-doc`).
Consumers can then simply reference the package by its original name (e.g.,
`foo-doc`).
--
2.53.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260730073805.396068-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-07-30 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 7:38 'Felix Moessbauer' via isar-users [this message]
2026-07-31 8:59 ` Zhihang Wei
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=20260730073805.396068-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
/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