manuals: replace unnecessary uses of 'yocto_docs' by internal references

These :yocto_docs: references were making external references
to another section of the manual, using the https://docs.yoctoproject.org
website. It's actually better to use internal references (:doc: for an
entire document, and :ref: for a specific section, as they will cause
an error in Sphinx if one day they are no longer valid.

(From yocto-docs rev: 0beff9dea986a2ea4b496180b29a99490416eeeb)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2023-02-08 21:31:16 +01:00
committed by Richard Purdie
parent 76eae50370
commit 5b02cfb3e7
3 changed files with 4 additions and 4 deletions

View File

@@ -173,7 +173,7 @@ Here is a list of resources you might find helpful:
- :yocto_wiki:`FAQ </FAQ>`: A list of commonly asked
questions and their answers.
- :yocto_docs:`Release Information </migration-guides/>`:
- :doc:`Release Information </migration-guides/index>`:
Migration guides, release notes, new features, updates and known issues
for the current and past releases of the Yocto Project.

View File

@@ -8481,7 +8481,7 @@ system and gives an overview of their function and contents.
responsibility to ensure that the toolchain is compatible with the
default toolchain. Using older or newer versions of these
components might cause build problems. See
:yocto_docs:`Release Information </migration-guides/>` for your
:doc:`Release Information </migration-guides/index>` for your
version of the Yocto Project, to find the specific components with
which the toolchain must be compatible.

View File

@@ -24,8 +24,8 @@ reproducibility matters. The primary focus of the project is the ability to
detect security issues being introduced. However, from a Yocto Project
perspective, it is also hugely important that our builds are deterministic. When
you build a given input set of metadata, we expect you to get consistent output.
This has always been a key focus but, :yocto_docs:`since release 3.1 ("dunfell")
</ref-manual/migration-3.1.html#reproducible-builds-now-enabled-by-default>`,
This has always been a key focus but, :ref:`since release 3.1 ("dunfell")
<migration-guides/migration-3.1:reproducible builds now enabled by default>`,
it is now true down to the binary level including timestamps.
For example, at some point in the future life of a product, you find that you