diff options
Diffstat (limited to 'documentation/migration-guides/migration-4.0.rst')
-rw-r--r-- | documentation/migration-guides/migration-4.0.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/migration-guides/migration-4.0.rst b/documentation/migration-guides/migration-4.0.rst index b5bd57c312..0e9e741458 100644 --- a/documentation/migration-guides/migration-4.0.rst +++ b/documentation/migration-guides/migration-4.0.rst | |||
@@ -68,7 +68,7 @@ changes and you need to review them before committing. An example warning | |||
68 | looks like:: | 68 | looks like:: |
69 | 69 | ||
70 | poky/scripts/lib/devtool/upgrade.py needs further work at line 275 since it contains abort | 70 | poky/scripts/lib/devtool/upgrade.py needs further work at line 275 since it contains abort |
71 | 71 | ||
72 | Fetching changes | 72 | Fetching changes |
73 | ~~~~~~~~~~~~~~~~ | 73 | ~~~~~~~~~~~~~~~~ |
74 | 74 | ||
@@ -111,7 +111,7 @@ License changes | |||
111 | If they do not, by default a warning will be shown. A | 111 | If they do not, by default a warning will be shown. A |
112 | :oe_git:`convert-spdx-licenses.py </openembedded-core/tree/scripts/contrib/convert-spdx-licenses.py>` | 112 | :oe_git:`convert-spdx-licenses.py </openembedded-core/tree/scripts/contrib/convert-spdx-licenses.py>` |
113 | script can be used to update your recipes. | 113 | script can be used to update your recipes. |
114 | 114 | ||
115 | - :term:`INCOMPATIBLE_LICENSE` should now use `SPDX identifiers <https://spdx.org/licenses/>`__. | 115 | - :term:`INCOMPATIBLE_LICENSE` should now use `SPDX identifiers <https://spdx.org/licenses/>`__. |
116 | Additionally, wildcarding is now limited to specifically supported values - | 116 | Additionally, wildcarding is now limited to specifically supported values - |
117 | see the :term:`INCOMPATIBLE_LICENSE` documentation for further information. | 117 | see the :term:`INCOMPATIBLE_LICENSE` documentation for further information. |
@@ -121,7 +121,7 @@ License changes | |||
121 | which can cause signature issues for users. In addition the ``available_licenses()`` | 121 | which can cause signature issues for users. In addition the ``available_licenses()`` |
122 | function has been removed from the :ref:`ref-classes-license` class as | 122 | function has been removed from the :ref:`ref-classes-license` class as |
123 | it is no longer needed. | 123 | it is no longer needed. |
124 | 124 | ||
125 | Removed recipes | 125 | Removed recipes |
126 | ~~~~~~~~~~~~~~~ | 126 | ~~~~~~~~~~~~~~~ |
127 | 127 | ||
@@ -136,11 +136,11 @@ The following recipes have been removed in this release: | |||
136 | 136 | ||
137 | Python changes | 137 | Python changes |
138 | ~~~~~~~~~~~~~~ | 138 | ~~~~~~~~~~~~~~ |
139 | 139 | ||
140 | - ``distutils`` has been deprecated upstream in Python 3.10 and thus the ``distutils*`` | 140 | - ``distutils`` has been deprecated upstream in Python 3.10 and thus the ``distutils*`` |
141 | classes have been moved to ``meta-python``. Recipes that inherit the ``distutils*`` | 141 | classes have been moved to ``meta-python``. Recipes that inherit the ``distutils*`` |
142 | classes should be updated to inherit ``setuptools*`` equivalents instead. | 142 | classes should be updated to inherit ``setuptools*`` equivalents instead. |
143 | 143 | ||
144 | - The Python package build process is now based on `wheels <https://pythonwheels.com/>`__. | 144 | - The Python package build process is now based on `wheels <https://pythonwheels.com/>`__. |
145 | The new Python packaging classes that should be used are | 145 | The new Python packaging classes that should be used are |
146 | :ref:`ref-classes-python_flit_core`, :ref:`ref-classes-python_setuptools_build_meta` | 146 | :ref:`ref-classes-python_flit_core`, :ref:`ref-classes-python_setuptools_build_meta` |
@@ -159,7 +159,7 @@ Prelink removed | |||
159 | Prelink has been dropped by ``glibc`` upstream in 2.36. It already caused issues with | 159 | Prelink has been dropped by ``glibc`` upstream in 2.36. It already caused issues with |
160 | binary corruption, has a number of open bugs and is of questionable benefit | 160 | binary corruption, has a number of open bugs and is of questionable benefit |
161 | without disabling load address randomization and PIE executables. | 161 | without disabling load address randomization and PIE executables. |
162 | 162 | ||
163 | We disabled prelinking by default in the honister (3.4) release, but left it able | 163 | We disabled prelinking by default in the honister (3.4) release, but left it able |
164 | to be enabled if desired. However, without glibc support it cannot be maintained | 164 | to be enabled if desired. However, without glibc support it cannot be maintained |
165 | any further, so all of the prelinking functionality has been removed in this release. | 165 | any further, so all of the prelinking functionality has been removed in this release. |
@@ -170,7 +170,7 @@ reference(s). | |||
170 | Reproducible as standard | 170 | Reproducible as standard |
171 | ~~~~~~~~~~~~~~~~~~~~~~~~ | 171 | ~~~~~~~~~~~~~~~~~~~~~~~~ |
172 | 172 | ||
173 | Reproducibility is now considered as standard functionality, thus the | 173 | Reproducibility is now considered as standard functionality, thus the |
174 | ``reproducible`` class has been removed and its previous contents merged into the | 174 | ``reproducible`` class has been removed and its previous contents merged into the |
175 | :ref:`ref-classes-base` class. If you have references in your configuration to | 175 | :ref:`ref-classes-base` class. If you have references in your configuration to |
176 | ``reproducible`` in :term:`INHERIT`, :term:`USER_CLASSES` etc. then they should be | 176 | ``reproducible`` in :term:`INHERIT`, :term:`USER_CLASSES` etc. then they should be |
@@ -212,7 +212,7 @@ and :ref:`bitbake-user-manual/bitbake-user-manual-metadata:removal (override sty | |||
212 | 212 | ||
213 | Miscellaneous changes | 213 | Miscellaneous changes |
214 | ~~~~~~~~~~~~~~~~~~~~~ | 214 | ~~~~~~~~~~~~~~~~~~~~~ |
215 | 215 | ||
216 | - ``blacklist.bbclass`` is removed and the functionality moved to the | 216 | - ``blacklist.bbclass`` is removed and the functionality moved to the |
217 | :ref:`ref-classes-base` class with a more descriptive | 217 | :ref:`ref-classes-base` class with a more descriptive |
218 | ``varflag`` variable named :term:`SKIP_RECIPE` which will use the `bb.parse.SkipRecipe()` | 218 | ``varflag`` variable named :term:`SKIP_RECIPE` which will use the `bb.parse.SkipRecipe()` |
@@ -252,7 +252,7 @@ Miscellaneous changes | |||
252 | - The ``cortexa72-crc`` and ``cortexa72-crc-crypto`` tunes have been removed since | 252 | - The ``cortexa72-crc`` and ``cortexa72-crc-crypto`` tunes have been removed since |
253 | the crc extension is now enabled by default for cortexa72. Replace any references to | 253 | the crc extension is now enabled by default for cortexa72. Replace any references to |
254 | these with ``cortexa72`` and ``cortexa72-crypto`` respectively. | 254 | these with ``cortexa72`` and ``cortexa72-crypto`` respectively. |
255 | 255 | ||
256 | - The Python development shell (previously known as ``devpyshell``) feature has been | 256 | - The Python development shell (previously known as ``devpyshell``) feature has been |
257 | renamed to ``pydevshell``. To start it you should now run:: | 257 | renamed to ``pydevshell``. To start it you should now run:: |
258 | 258 | ||
@@ -261,7 +261,7 @@ Miscellaneous changes | |||
261 | - The ``packagegroups-core-full-cmdline-libs`` packagegroup is no longer produced, as | 261 | - The ``packagegroups-core-full-cmdline-libs`` packagegroup is no longer produced, as |
262 | libraries should normally be brought in via dependencies. If you have any references | 262 | libraries should normally be brought in via dependencies. If you have any references |
263 | to this then remove them. | 263 | to this then remove them. |
264 | 264 | ||
265 | - The :term:`TOPDIR` variable and the current working directory are no longer modified | 265 | - The :term:`TOPDIR` variable and the current working directory are no longer modified |
266 | when parsing recipes. Any code depending on the previous behaviour will no longer | 266 | when parsing recipes. Any code depending on the previous behaviour will no longer |
267 | work - change any such code to explicitly use appropriate path variables instead. | 267 | work - change any such code to explicitly use appropriate path variables instead. |