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-2.3.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-2.3.rst')
-rw-r--r-- | documentation/migration-guides/migration-2.3.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/migration-guides/migration-2.3.rst b/documentation/migration-guides/migration-2.3.rst index 6cdc209e35..f9bdf0d27b 100644 --- a/documentation/migration-guides/migration-2.3.rst +++ b/documentation/migration-guides/migration-2.3.rst | |||
@@ -35,7 +35,7 @@ Consider the following: | |||
35 | As an example, see the ``dbus`` recipe. You will see that this recipe | 35 | As an example, see the ``dbus`` recipe. You will see that this recipe |
36 | has a ``pkg_postinst`` that calls ``systemctl`` if "systemd" is in | 36 | has a ``pkg_postinst`` that calls ``systemctl`` if "systemd" is in |
37 | :term:`DISTRO_FEATURES`. In the example, | 37 | :term:`DISTRO_FEATURES`. In the example, |
38 | ``systemd-systemctl-native`` is added to ``PACKAGE_WRITE_DEPS``, | 38 | ``systemd-systemctl-native`` is added to :term:`PACKAGE_WRITE_DEPS`, |
39 | which is also conditional on "systemd" being in ``DISTRO_FEATURES``. | 39 | which is also conditional on "systemd" being in ``DISTRO_FEATURES``. |
40 | 40 | ||
41 | - Examine Recipes that Use ``SSTATEPOSTINSTFUNCS``: You need to | 41 | - Examine Recipes that Use ``SSTATEPOSTINSTFUNCS``: You need to |
@@ -136,7 +136,7 @@ The following changes to scripts took place: | |||
136 | removed because the script was found to be deleting files it should | 136 | removed because the script was found to be deleting files it should |
137 | not have, which lead to broken build trees. Rather than trying to | 137 | not have, which lead to broken build trees. Rather than trying to |
138 | delete portions of :term:`TMPDIR` and getting it wrong, | 138 | delete portions of :term:`TMPDIR` and getting it wrong, |
139 | it is recommended that you delete ``TMPDIR`` and have it restored | 139 | it is recommended that you delete :term:`TMPDIR` and have it restored |
140 | from shared state (sstate) on subsequent builds. | 140 | from shared state (sstate) on subsequent builds. |
141 | 141 | ||
142 | - ``wipe-sysroot``: The ``wipe-sysroot`` script has been removed as | 142 | - ``wipe-sysroot``: The ``wipe-sysroot`` script has been removed as |
@@ -200,10 +200,10 @@ The following changes took place for BitBake: | |||
200 | section in the BitBake | 200 | section in the BitBake |
201 | User Manual for additional information. | 201 | User Manual for additional information. |
202 | 202 | ||
203 | - ``BB_SETSCENE_VERIFY_FUNCTION`` and ``BB_SETSCENE_VERIFY_FUNCTION2`` | 203 | - ``BB_SETSCENE_VERIFY_FUNCTION`` and :term:`BB_SETSCENE_VERIFY_FUNCTION2` |
204 | Removed: Because the mechanism they were part of is no longer | 204 | Removed: Because the mechanism they were part of is no longer |
205 | necessary with recipe-specific sysroots, the | 205 | necessary with recipe-specific sysroots, the |
206 | ``BB_SETSCENE_VERIFY_FUNCTION`` and ``BB_SETSCENE_VERIFY_FUNCTION2`` | 206 | ``BB_SETSCENE_VERIFY_FUNCTION`` and :term:`BB_SETSCENE_VERIFY_FUNCTION2` |
207 | variables have been removed. | 207 | variables have been removed. |
208 | 208 | ||
209 | .. _migration-2.3-absolute-symlinks: | 209 | .. _migration-2.3-absolute-symlinks: |
@@ -426,10 +426,10 @@ The following miscellaneous changes have occurred: | |||
426 | 426 | ||
427 | - If the :term:`DISTRO_VERSION` value contains | 427 | - If the :term:`DISTRO_VERSION` value contains |
428 | the value of the :term:`DATE` variable, which is the | 428 | the value of the :term:`DATE` variable, which is the |
429 | default between Poky releases, the ``DATE`` value is explicitly | 429 | default between Poky releases, the :term:`DATE` value is explicitly |
430 | excluded from ``/etc/issue`` and ``/etc/issue.net``, which is | 430 | excluded from ``/etc/issue`` and ``/etc/issue.net``, which is |
431 | displayed at the login prompt, in order to avoid conflicts with | 431 | displayed at the login prompt, in order to avoid conflicts with |
432 | Multilib enabled. Regardless, the ``DATE`` value is inaccurate if the | 432 | Multilib enabled. Regardless, the :term:`DATE` value is inaccurate if the |
433 | ``base-files`` recipe is restored from shared state (sstate) rather | 433 | ``base-files`` recipe is restored from shared state (sstate) rather |
434 | than rebuilt. | 434 | than rebuilt. |
435 | 435 | ||
@@ -451,7 +451,7 @@ The following miscellaneous changes have occurred: | |||
451 | tools. | 451 | tools. |
452 | 452 | ||
453 | - The ``USE_LDCONFIG`` variable has been replaced with the "ldconfig" | 453 | - The ``USE_LDCONFIG`` variable has been replaced with the "ldconfig" |
454 | ``DISTRO_FEATURES`` feature. Distributions that previously set:: | 454 | :term:`DISTRO_FEATURES` feature. Distributions that previously set:: |
455 | 455 | ||
456 | USE_LDCONFIG = "0" | 456 | USE_LDCONFIG = "0" |
457 | 457 | ||
@@ -494,12 +494,12 @@ The following miscellaneous changes have occurred: | |||
494 | information. | 494 | information. |
495 | 495 | ||
496 | - All native and nativesdk recipes now use a separate | 496 | - All native and nativesdk recipes now use a separate |
497 | ``DISTRO_FEATURES`` value instead of sharing the value used by | 497 | :term:`DISTRO_FEATURES` value instead of sharing the value used by |
498 | recipes for the target, in order to avoid unnecessary rebuilds. | 498 | recipes for the target, in order to avoid unnecessary rebuilds. |
499 | 499 | ||
500 | The ``DISTRO_FEATURES`` for ``native`` recipes is | 500 | The :term:`DISTRO_FEATURES` for ``native`` recipes is |
501 | :term:`DISTRO_FEATURES_NATIVE` added to | 501 | :term:`DISTRO_FEATURES_NATIVE` added to |
502 | an intersection of ``DISTRO_FEATURES`` and | 502 | an intersection of :term:`DISTRO_FEATURES` and |
503 | :term:`DISTRO_FEATURES_FILTER_NATIVE`. | 503 | :term:`DISTRO_FEATURES_FILTER_NATIVE`. |
504 | 504 | ||
505 | For nativesdk recipes, the corresponding variables are | 505 | For nativesdk recipes, the corresponding variables are |