From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 2/7] ref-manual: variables: mention new CDN for SSTATE_MIRRORS
Date: Tue, 14 Nov 2023 17:49:37 +0100 [thread overview]
Message-ID: <20231114164942.133472-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231114164942.133472-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 58a763cb3a..5a34ea7856 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7619,6 +7619,16 @@ system and gives an overview of their function and contents.
file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
file://.* file:///some-local-dir/sstate/PATH"
+ The Yocto Project actually shares the cache data objects built by its
+ autobuilder::
+
+ SSTATE_MIRRORS ?= "file://.* http://cdn.jsdelivr.net/yocto/sstate/all/PATH;downloadfilename=PATH"
+
+ As such binary artifacts are built for the generic QEMU machines
+ supported by the various Poky releases, they are less likely to be
+ reusable in real projects building binaries optimized for a specific
+ CPU family.
+
:term:`SSTATE_SCAN_FILES`
Controls the list of files the OpenEmbedded build system scans for
hardcoded installation paths. The variable uses a space-separated
--
2.34.1
next prev parent reply other threads:[~2023-11-14 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:49 [kirkstone][PATCH 0/7] kirkstone backports michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 1/7] ref-manual: variables: document OEQA_REPRODUCIBLE_* variables michael.opdenacker
2023-11-14 16:49 ` michael.opdenacker [this message]
2023-11-14 16:49 ` [kirkstone][PATCH 3/7] ref-manual: variables: add RECIPE_MAINTAINER michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 4/7] overview-manual: concepts: Add Bitbake Tasks Map michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 5/7] ref-manual: update SDK_NAME variable documentation michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 6/7] ref-manual: classes: explain cml1 class name michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 7/7] manuals: update class references michael.opdenacker
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=20231114164942.133472-3-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).