From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: "Michael Opdenacker" <michael.opdenacker@bootlin.com>,
"Simone Weiß" <simone.p.weiss@posteo.com>
Subject: [kirkstone][PATCH 2/6] dev-manual: start.rst: update use of Download page
Date: Fri, 12 Jan 2024 17:53:07 +0100 [thread overview]
Message-ID: <20240112165311.3554201-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240112165311.3554201-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Simone Weiß <simone.p.weiss@posteo.com>
The yocto website has changed its structure. Update the section for
Accessing the Downloads page to match the new structure.
Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/dev-manual/start.rst | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 3bc4244595..5a81506a9b 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -642,7 +642,7 @@ Follow these steps to locate and download a particular tarball:
Using the Downloads Page
------------------------
-The :yocto_home:`Yocto Project Website <>` uses a "DOWNLOADS" page
+The :yocto_home:`Yocto Project Website <>` uses a "RELEASES" page
from which you can locate and download tarballs of any Yocto Project
release. Rather than Git repositories, these files represent snapshot
tarballs similar to the tarballs located in the Index of Releases
@@ -651,11 +651,13 @@ described in the ":ref:`dev-manual/start:accessing index of releases`" section.
1. *Go to the Yocto Project Website:* Open The
:yocto_home:`Yocto Project Website <>` in your browser.
-2. *Get to the Downloads Area:* Select the "DOWNLOADS" item from the
- pull-down "SOFTWARE" tab menu near the top of the page.
+#. *Get to the Downloads Area:* Select the "RELEASES" item from the
+ pull-down "DEVELOPMENT" tab menu near the top of the page.
-3. *Select a Yocto Project Release:* Use the menu next to "RELEASE" to
- display and choose a recent or past supported Yocto Project release
+#. *Select a Yocto Project Release:* On the top of the "RELEASE" page currently
+ supported releases are displayed, further down past supported Yocto Project
+ releases are visible. The "Download" links in the rows of the table there
+ will lead to the download tarballs for the release
(e.g. &DISTRO_NAME_NO_CAP;, &DISTRO_NAME_NO_CAP_MINUS_ONE;, and so forth).
.. note::
@@ -666,9 +668,9 @@ described in the ":ref:`dev-manual/start:accessing index of releases`" section.
You can use the "RELEASE ARCHIVE" link to reveal a menu of all Yocto
Project releases.
-4. *Download Tools or Board Support Packages (BSPs):* From the
- "DOWNLOADS" page, you can download tools or BSPs as well. Just scroll
- down the page and look for what you need.
+#. *Download Tools or Board Support Packages (BSPs):* Next to the tarballs you
+ will find download tools or BSPs as well. Just select a Yocto Project
+ release and look for what you need.
Cloning and Checking Out Branches
=================================
--
2.34.1
next prev parent reply other threads:[~2024-01-12 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 16:53 [kirkstone][PATCH 0/6] documentation backports michael.opdenacker
2024-01-12 16:53 ` [kirkstone][PATCH 1/6] contributor-guide: use "apt" instead of "aptitude" michael.opdenacker
2024-01-12 16:53 ` michael.opdenacker [this message]
2024-01-12 16:53 ` [kirkstone][PATCH 3/6] ref-manual: classes: remove insserv bbclass michael.opdenacker
2024-01-12 16:53 ` [kirkstone][PATCH 4/6] ref-manual: resources: sync with master branch michael.opdenacker
2024-01-12 16:53 ` [kirkstone][PATCH 5/6] manuals: document VSCode extension michael.opdenacker
2024-01-12 16:53 ` [kirkstone][PATCH 6/6] documentation: Add UBOOT_BINARY, extend UBOOT_CONFIG 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=20240112165311.3554201-3-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=simone.p.weiss@posteo.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