diff options
author | Quentin Schulz <foss@0leil.net> | 2021-05-27 20:41:17 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-06-19 16:54:01 +0100 |
commit | 7d3f57cfd2e4322bcd96d67d330124f221a9aedd (patch) | |
tree | 5d07321b7c8bc59bb7fcc0372fab8b7a1966cf06 /documentation/migration-guides/migration-1.6.rst | |
parent | 7a9b74e9d2a5cf3b1fb3ac7565c50eae6e0d4632 (diff) | |
download | poky-7d3f57cfd2e4322bcd96d67d330124f221a9aedd.tar.gz |
docs: replace ``FOO`` by :term:`FOO` where possible
If a variable has a glossary entry and some rST files write about those
variables, it's better to point to the glossary entry instead of just
highlighting it by surrounding it with two tick quotes.
This was automated by the following python script:
"""
import re
from pathlib import Path
with open('objects.inv.txt', 'r') as f:
objects = f.readlines()
with open('bitbake-objects.inv.txt', 'r') as f:
objects = objects + f.readlines()
re_term = re.compile(r'variables.html#term-([A-Z_0-9]*)')
terms = []
for obj in objects:
match = re_term.search(obj)
if match and match.group(1):
terms.append(match.group(1))
for rst in Path('.').rglob('*.rst'):
with open(rst, 'r') as f:
content = "".joing(f.readlines())
for term in terms:
content = re.sub(r'``({})``(?!.*\s*[~-]+)'.format(term), r':term:`\1`', content)
with open(rst, 'w') as f:
f.write(content)
"""
(From yocto-docs rev: ba49d9babfcb84bc5c26a68c8c3880a1d9c236d3)
Signed-off-by: Quentin Schulz <foss@0leil.net>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/migration-guides/migration-1.6.rst')
-rw-r--r-- | documentation/migration-guides/migration-1.6.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/migration-guides/migration-1.6.rst b/documentation/migration-guides/migration-1.6.rst index 1408e12c23..eea3d17676 100644 --- a/documentation/migration-guides/migration-1.6.rst +++ b/documentation/migration-guides/migration-1.6.rst | |||
@@ -61,7 +61,7 @@ If you do not specify a branch, BitBake looks in the default "master" branch. | |||
61 | 61 | ||
62 | Alternatively, if you need to bypass this check (e.g. if you are | 62 | Alternatively, if you need to bypass this check (e.g. if you are |
63 | fetching a revision corresponding to a tag that is not on any branch), | 63 | fetching a revision corresponding to a tag that is not on any branch), |
64 | you can add ";nobranch=1" to the end of the URL within ``SRC_URI``. | 64 | you can add ";nobranch=1" to the end of the URL within :term:`SRC_URI`. |
65 | 65 | ||
66 | .. _migration-1.6-bitbake-deps: | 66 | .. _migration-1.6-bitbake-deps: |
67 | 67 | ||
@@ -134,9 +134,9 @@ OpenEmbedded build system variables, see the ":doc:`/ref-manual/variables`" Chap | |||
134 | 134 | ||
135 | :term:`TMPDIR` can no longer be on an NFS mount. NFS does | 135 | :term:`TMPDIR` can no longer be on an NFS mount. NFS does |
136 | not offer full POSIX locking and inode consistency and can cause | 136 | not offer full POSIX locking and inode consistency and can cause |
137 | unexpected issues if used to store ``TMPDIR``. | 137 | unexpected issues if used to store :term:`TMPDIR`. |
138 | 138 | ||
139 | The check for this occurs on startup. If ``TMPDIR`` is detected on an | 139 | The check for this occurs on startup. If :term:`TMPDIR` is detected on an |
140 | NFS mount, an error occurs. | 140 | NFS mount, an error occurs. |
141 | 141 | ||
142 | .. _migration-1.6-variable-changes-PRINC: | 142 | .. _migration-1.6-variable-changes-PRINC: |
@@ -274,7 +274,7 @@ In addition to ``core-image-basic`` being renamed, | |||
274 | Licensing | 274 | Licensing |
275 | --------- | 275 | --------- |
276 | 276 | ||
277 | The top-level ``LICENSE`` file has been changed to better describe the | 277 | The top-level :term:`LICENSE` file has been changed to better describe the |
278 | license of the various components of :term:`OpenEmbedded-Core (OE-Core)`. However, | 278 | license of the various components of :term:`OpenEmbedded-Core (OE-Core)`. However, |
279 | the licensing itself remains unchanged. | 279 | the licensing itself remains unchanged. |
280 | 280 | ||
@@ -284,7 +284,7 @@ recipes point to this file within | |||
284 | ``${COREBASE}/LICENSE``) and thus the accompanying checksum must be | 284 | ``${COREBASE}/LICENSE``) and thus the accompanying checksum must be |
285 | changed from 3f40d7994397109285ec7b81fdeb3b58 to | 285 | changed from 3f40d7994397109285ec7b81fdeb3b58 to |
286 | 4d92cd373abda3937c2bc47fbc49d690. A better alternative is to have | 286 | 4d92cd373abda3937c2bc47fbc49d690. A better alternative is to have |
287 | ``LIC_FILES_CHKSUM`` point to a file describing the license that is | 287 | :term:`LIC_FILES_CHKSUM` point to a file describing the license that is |
288 | distributed with the source that the recipe is building, if possible, | 288 | distributed with the source that the recipe is building, if possible, |
289 | rather than pointing to ``${COREBASE}/LICENSE``. | 289 | rather than pointing to ``${COREBASE}/LICENSE``. |
290 | 290 | ||
@@ -297,7 +297,7 @@ The "-fpermissive" option has been removed from the default | |||
297 | :term:`CFLAGS` value. You need to take action on | 297 | :term:`CFLAGS` value. You need to take action on |
298 | individual recipes that fail when building with this option. You need to | 298 | individual recipes that fail when building with this option. You need to |
299 | either patch the recipes to fix the issues reported by the compiler, or | 299 | either patch the recipes to fix the issues reported by the compiler, or |
300 | you need to add "-fpermissive" to ``CFLAGS`` in the recipes. | 300 | you need to add "-fpermissive" to :term:`CFLAGS` in the recipes. |
301 | 301 | ||
302 | .. _migration-1.6-custom-images: | 302 | .. _migration-1.6-custom-images: |
303 | 303 | ||