summaryrefslogtreecommitdiffstats
path: root/documentation/migration-guides/migration-4.1.rst
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2023-01-05 08:34:26 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-01-06 17:39:09 +0000
commit8b1909aa6f7a51a878dc3d4a9223403ad3e164a9 (patch)
treee1418f545ad6640afb5fde004696eef2a9e6e67b /documentation/migration-guides/migration-4.1.rst
parentae280972ffba62d7ed839b692957f61b0955cbca (diff)
downloadpoky-8b1909aa6f7a51a878dc3d4a9223403ad3e164a9.tar.gz
manuals: simplify references to classes
Now that .bbclass is removed from class section titles. We can now have, for example, :ref:`ref-classes-insane` instead of :ref:`insane <ref-classes-insane>`. Then, when necessary, rework paragraphs so that they have lines of even length, not exceeding 80 characters. (From yocto-docs rev: e76190e3be78c1e483bec0469f1e437dbf8f3791) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Suggested-by: Quentin Schulz <foss+yocto@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/migration-guides/migration-4.1.rst')
-rw-r--r--documentation/migration-guides/migration-4.1.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/migration-guides/migration-4.1.rst b/documentation/migration-guides/migration-4.1.rst
index 8b9db40ddc..86721b9873 100644
--- a/documentation/migration-guides/migration-4.1.rst
+++ b/documentation/migration-guides/migration-4.1.rst
@@ -92,7 +92,7 @@ now cause an error::
92 92
93 INHERIT += "testimage" 93 INHERIT += "testimage"
94 94
95Since :ref:`testimage <ref-classes-testimage>` is a class intended solely to 95Since :ref:`ref-classes-testimage` is a class intended solely to
96affect image recipes, this would be correctly specified as:: 96affect image recipes, this would be correctly specified as::
97 97
98 IMAGE_CLASSES += "testimage" 98 IMAGE_CLASSES += "testimage"
@@ -154,16 +154,16 @@ Miscellaneous changes
154 you can set :term:`WATCHDOG_TIMEOUT` to the desired timeout in seconds. Note 154 you can set :term:`WATCHDOG_TIMEOUT` to the desired timeout in seconds. Note
155 that the same :term:`WATCHDOG_TIMEOUT` variable also specifies the timeout used 155 that the same :term:`WATCHDOG_TIMEOUT` variable also specifies the timeout used
156 for the ``watchdog`` tool (if that is being built). 156 for the ``watchdog`` tool (if that is being built).
157- The :ref:`image-buildinfo <ref-classes-image-buildinfo>` class now writes to 157- The :ref:`ref-classes-image-buildinfo` class now writes to
158 ``${sysconfdir}/buildinfo`` instead of ``${sysconfdir}/build`` by default (i.e. 158 ``${sysconfdir}/buildinfo`` instead of ``${sysconfdir}/build`` by default (i.e.
159 the default value of :term:`IMAGE_BUILDINFO_FILE` has been changed). If you have 159 the default value of :term:`IMAGE_BUILDINFO_FILE` has been changed). If you have
160 code that reads this from images at build or runtime you will need to update it 160 code that reads this from images at build or runtime you will need to update it
161 or specify your own value for :term:`IMAGE_BUILDINFO_FILE`. 161 or specify your own value for :term:`IMAGE_BUILDINFO_FILE`.
162- In the :ref:`archiver <ref-classes-archiver>` class, the default 162- In the :ref:`ref-classes-archiver` class, the default
163 ``ARCHIVER_OUTDIR`` value no longer includes the :term:`MACHINE` value in order 163 ``ARCHIVER_OUTDIR`` value no longer includes the :term:`MACHINE` value in order
164 to avoid the archive task running multiple times in a multiconfig setup. If you 164 to avoid the archive task running multiple times in a multiconfig setup. If you
165 have custom code that does something with the files archived by the 165 have custom code that does something with the files archived by the
166 :ref:`archiver <ref-classes-archiver>` class then you may need to adjust it to 166 :ref:`ref-classes-archiver` class then you may need to adjust it to
167 the new structure. 167 the new structure.
168- If you are not using `systemd` then udev is now configured to use labels 168- If you are not using `systemd` then udev is now configured to use labels
169 (``LABEL`` or ``PARTLABEL``) to set the mount point for the device. For example:: 169 (``LABEL`` or ``PARTLABEL``) to set the mount point for the device. For example::
@@ -194,7 +194,7 @@ Miscellaneous changes
194 :term:`PACKAGECONFIG`. If you are customising this file you will need to 194 :term:`PACKAGECONFIG`. If you are customising this file you will need to
195 update your customisations. 195 update your customisations.
196- With the introduction of picobuild in 196- With the introduction of picobuild in
197 :ref:`python_pep517 <ref-classes-python_pep517>`, The ``PEP517_BUILD_API`` 197 :ref:`ref-classes-python_pep517`, The ``PEP517_BUILD_API``
198 variable is no longer supported. If you have any references to this variable 198 variable is no longer supported. If you have any references to this variable
199 you should remove them. 199 you should remove them.
200 200