diff options
author | Antonin Godard <antonin.godard@bootlin.com> | 2025-04-09 11:55:42 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-04-21 21:15:29 +0100 |
commit | 841965f127407dc8af56382b99d56e37ff67eea5 (patch) | |
tree | f7d42b3e99ec94ff1ca88e54cc1bc5fb378e0e51 /documentation | |
parent | 76f887eb12baee0c2e6554e131fe4f1e0854d84e (diff) | |
download | poky-841965f127407dc8af56382b99d56e37ff67eea5.tar.gz |
Fix dead links that use the DISTRO macro
After introducing the DISTRO_LATEST_TAG and DISTRO_REL_LATEST_TAG
macros, use them in links that currently use DISTRO/DISTRO_REL_TAG. When
building for the tip of a branch, this will replace the current A.B.999
in links to the latest existing tag.
The links were found across the documentation by running 'grep -r
"http.*5\.2\.999"' inside the _build/html output after building the
docs.
[YOCTO #14802]
(From yocto-docs rev: 29be069ebbf2c55d72fc51d99ed5a558af37c05e)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/bsp-guide/bsp.rst | 2 | ||||
-rw-r--r-- | documentation/dev-manual/qemu.rst | 2 | ||||
-rw-r--r-- | documentation/dev-manual/start.rst | 2 | ||||
-rw-r--r-- | documentation/ref-manual/system-requirements.rst | 2 | ||||
-rw-r--r-- | documentation/ref-manual/terms.rst | 2 | ||||
-rw-r--r-- | documentation/sdk-manual/appendix-obtain.rst | 6 | ||||
-rw-r--r-- | documentation/sdk-manual/extensible.rst | 2 | ||||
-rw-r--r-- | documentation/sdk-manual/intro.rst | 4 | ||||
-rw-r--r-- | documentation/sdk-manual/using.rst | 2 |
9 files changed, 12 insertions, 12 deletions
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst index 11ca5d8b76..3e484aa473 100644 --- a/documentation/bsp-guide/bsp.rst +++ b/documentation/bsp-guide/bsp.rst | |||
@@ -166,7 +166,7 @@ section. | |||
166 | BSPs, which are maintained in their own layers or in layers designed | 166 | BSPs, which are maintained in their own layers or in layers designed |
167 | to contain several BSPs. To get an idea of machine support through | 167 | to contain several BSPs. To get an idea of machine support through |
168 | BSP layers, you can look at the | 168 | BSP layers, you can look at the |
169 | :yocto_dl:`index of machines </releases/yocto/yocto-&DISTRO;/machines>` | 169 | :yocto_dl:`index of machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines>` |
170 | for the release. | 170 | for the release. |
171 | 171 | ||
172 | #. *Optionally Clone the meta-intel BSP Layer:* If your hardware is | 172 | #. *Optionally Clone the meta-intel BSP Layer:* If your hardware is |
diff --git a/documentation/dev-manual/qemu.rst b/documentation/dev-manual/qemu.rst index 030bd55143..92c93a82ab 100644 --- a/documentation/dev-manual/qemu.rst +++ b/documentation/dev-manual/qemu.rst | |||
@@ -75,7 +75,7 @@ available. Follow these general steps to run QEMU: | |||
75 | your :term:`Build Directory`. | 75 | your :term:`Build Directory`. |
76 | 76 | ||
77 | - If you have not built an image, you can go to the | 77 | - If you have not built an image, you can go to the |
78 | :yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu/>` area and download a | 78 | :yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu/>` area and download a |
79 | pre-built image that matches your architecture and can be run on | 79 | pre-built image that matches your architecture and can be run on |
80 | QEMU. | 80 | QEMU. |
81 | 81 | ||
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst index 05827610b7..0f015d4340 100644 --- a/documentation/dev-manual/start.rst +++ b/documentation/dev-manual/start.rst | |||
@@ -615,7 +615,7 @@ Accessing Source Archives | |||
615 | The Yocto Project also provides source archives of its releases, which | 615 | The Yocto Project also provides source archives of its releases, which |
616 | are available on :yocto_dl:`/releases/yocto/`. Then, choose the subdirectory | 616 | are available on :yocto_dl:`/releases/yocto/`. Then, choose the subdirectory |
617 | containing the release you wish to use, for example | 617 | containing the release you wish to use, for example |
618 | :yocto_dl:`yocto-&DISTRO; </releases/yocto/yocto-&DISTRO;/>`. | 618 | :yocto_dl:`&DISTRO_REL_LATEST_TAG; </releases/yocto/&DISTRO_REL_LATEST_TAG;/>`. |
619 | 619 | ||
620 | You will find there source archives of individual components (if you wish | 620 | You will find there source archives of individual components (if you wish |
621 | to use them individually), and of the corresponding Poky release bundling | 621 | to use them individually), and of the corresponding Poky release bundling |
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst index 04d2674efd..b64a13320a 100644 --- a/documentation/ref-manual/system-requirements.rst +++ b/documentation/ref-manual/system-requirements.rst | |||
@@ -393,7 +393,7 @@ If you would prefer not to use the ``install-buildtools`` script, you can instea | |||
393 | download and run a pre-built :term:`buildtools` installer yourself with the following | 393 | download and run a pre-built :term:`buildtools` installer yourself with the following |
394 | steps: | 394 | steps: |
395 | 395 | ||
396 | #. Go to :yocto_dl:`/releases/yocto/yocto-&DISTRO;/buildtools/`, locate and | 396 | #. Go to :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/buildtools/`, locate and |
397 | download the ``.sh`` file corresponding to your host architecture | 397 | download the ``.sh`` file corresponding to your host architecture |
398 | and to :term:`buildtools`, :term:`buildtools-extended` or :term:`buildtools-make`. | 398 | and to :term:`buildtools`, :term:`buildtools-extended` or :term:`buildtools-make`. |
399 | 399 | ||
diff --git a/documentation/ref-manual/terms.rst b/documentation/ref-manual/terms.rst index b18c4183b6..9d765c89c8 100644 --- a/documentation/ref-manual/terms.rst +++ b/documentation/ref-manual/terms.rst | |||
@@ -452,7 +452,7 @@ universal, the list includes them just in case: | |||
452 | the Source Directory, if you do, the top-level directory name of the | 452 | the Source Directory, if you do, the top-level directory name of the |
453 | Source Directory is derived from the Yocto Project release tarball. | 453 | Source Directory is derived from the Yocto Project release tarball. |
454 | For example, downloading and unpacking poky tarballs from | 454 | For example, downloading and unpacking poky tarballs from |
455 | :yocto_dl:`/releases/yocto/&DISTRO_REL_TAG;/` | 455 | :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/` |
456 | results in a Source Directory whose root folder is named poky. | 456 | results in a Source Directory whose root folder is named poky. |
457 | 457 | ||
458 | 458 | ||
diff --git a/documentation/sdk-manual/appendix-obtain.rst b/documentation/sdk-manual/appendix-obtain.rst index d06d6ec6b5..a42cbc31bb 100644 --- a/documentation/sdk-manual/appendix-obtain.rst +++ b/documentation/sdk-manual/appendix-obtain.rst | |||
@@ -29,7 +29,7 @@ and then run the script to hand-install the toolchain. | |||
29 | Follow these steps to locate and hand-install the toolchain: | 29 | Follow these steps to locate and hand-install the toolchain: |
30 | 30 | ||
31 | #. *Go to the Installers Directory:* Go to | 31 | #. *Go to the Installers Directory:* Go to |
32 | :yocto_dl:`/releases/yocto/yocto-&DISTRO;/toolchain/` | 32 | :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/` |
33 | 33 | ||
34 | #. *Open the Folder for Your Build Host:* Open the folder that matches | 34 | #. *Open the Folder for Your Build Host:* Open the folder that matches |
35 | your :term:`Build Host` (i.e. | 35 | your :term:`Build Host` (i.e. |
@@ -201,7 +201,7 @@ Follow these steps to extract the root filesystem: | |||
201 | Image File:* You need to find and download the root filesystem image | 201 | Image File:* You need to find and download the root filesystem image |
202 | file that is appropriate for your target system. These files are kept | 202 | file that is appropriate for your target system. These files are kept |
203 | in machine-specific folders in the | 203 | in machine-specific folders in the |
204 | :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>` | 204 | :yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>` |
205 | in the "machines" directory. | 205 | in the "machines" directory. |
206 | 206 | ||
207 | The machine-specific folders of the "machines" directory contain | 207 | The machine-specific folders of the "machines" directory contain |
@@ -245,7 +245,7 @@ Follow these steps to extract the root filesystem: | |||
245 | 245 | ||
246 | Here is an example command that extracts the root filesystem | 246 | Here is an example command that extracts the root filesystem |
247 | from a previously built root filesystem image that was downloaded | 247 | from a previously built root filesystem image that was downloaded |
248 | from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`. | 248 | from the :yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>`. |
249 | This command extracts the root filesystem into the ``core2-64-sato`` | 249 | This command extracts the root filesystem into the ``core2-64-sato`` |
250 | directory:: | 250 | directory:: |
251 | 251 | ||
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index dcb02c4e00..e5e9e4a03b 100644 --- a/documentation/sdk-manual/extensible.rst +++ b/documentation/sdk-manual/extensible.rst | |||
@@ -87,7 +87,7 @@ Host` by running the ``*.sh`` installation script. | |||
87 | You can download a tarball installer, which includes the pre-built | 87 | You can download a tarball installer, which includes the pre-built |
88 | toolchain, the ``runqemu`` script, the internal build system, | 88 | toolchain, the ``runqemu`` script, the internal build system, |
89 | ``devtool``, and support files from the appropriate | 89 | ``devtool``, and support files from the appropriate |
90 | :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within the Index of | 90 | :yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within the Index of |
91 | Releases. Toolchains are available for several 32-bit and 64-bit | 91 | Releases. Toolchains are available for several 32-bit and 64-bit |
92 | architectures with the ``x86_64`` directories, respectively. The | 92 | architectures with the ``x86_64`` directories, respectively. The |
93 | toolchains the Yocto Project provides are based off the | 93 | toolchains the Yocto Project provides are based off the |
diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst index e8fd191dbc..fbfc8c2ac7 100644 --- a/documentation/sdk-manual/intro.rst +++ b/documentation/sdk-manual/intro.rst | |||
@@ -173,7 +173,7 @@ You just need to follow these general steps: | |||
173 | root filesystem images. | 173 | root filesystem images. |
174 | 174 | ||
175 | If you are going to develop your application on hardware, go to the | 175 | If you are going to develop your application on hardware, go to the |
176 | :yocto_dl:`machines </releases/yocto/yocto-&DISTRO;/machines/>` download area and choose a | 176 | :yocto_dl:`machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>` download area and choose a |
177 | target machine area from which to download the kernel image and root | 177 | target machine area from which to download the kernel image and root |
178 | filesystem. This download area could have several files in it that | 178 | filesystem. This download area could have several files in it that |
179 | support development using actual hardware. For example, the area | 179 | support development using actual hardware. For example, the area |
@@ -183,7 +183,7 @@ You just need to follow these general steps: | |||
183 | 183 | ||
184 | If you are going to develop your application and then run and test it | 184 | If you are going to develop your application and then run and test it |
185 | using the QEMU emulator, go to the | 185 | using the QEMU emulator, go to the |
186 | :yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu>` download area. From this | 186 | :yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu>` download area. From this |
187 | area, go down into the directory for your target architecture (e.g. | 187 | area, go down into the directory for your target architecture (e.g. |
188 | ``qemux86_64`` for an Intel-based 64-bit architecture). Download the | 188 | ``qemux86_64`` for an Intel-based 64-bit architecture). Download the |
189 | kernel, root filesystem, and any other files you need for your | 189 | kernel, root filesystem, and any other files you need for your |
diff --git a/documentation/sdk-manual/using.rst b/documentation/sdk-manual/using.rst index f1ff0c76ca..bfb306abf5 100644 --- a/documentation/sdk-manual/using.rst +++ b/documentation/sdk-manual/using.rst | |||
@@ -43,7 +43,7 @@ Host` by running the ``*.sh`` installation script. | |||
43 | 43 | ||
44 | You can download a tarball installer, which includes the pre-built | 44 | You can download a tarball installer, which includes the pre-built |
45 | toolchain, the ``runqemu`` script, and support files from the | 45 | toolchain, the ``runqemu`` script, and support files from the |
46 | appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within | 46 | appropriate :yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within |
47 | the Index of Releases. Toolchains are available for several 32-bit and | 47 | the Index of Releases. Toolchains are available for several 32-bit and |
48 | 64-bit architectures with the ``x86_64`` directories, respectively. The | 48 | 64-bit architectures with the ``x86_64`` directories, respectively. The |
49 | toolchains the Yocto Project provides are based off the | 49 | toolchains the Yocto Project provides are based off the |