diff options
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/migration-guides/migration-5.0.rst | 84 |
1 files changed, 76 insertions, 8 deletions
diff --git a/documentation/migration-guides/migration-5.0.rst b/documentation/migration-guides/migration-5.0.rst index 888a1c60d4..cf413300c2 100644 --- a/documentation/migration-guides/migration-5.0.rst +++ b/documentation/migration-guides/migration-5.0.rst | |||
@@ -80,7 +80,8 @@ Recipe changes | |||
80 | Deprecated variables | 80 | Deprecated variables |
81 | ~~~~~~~~~~~~~~~~~~~~ | 81 | ~~~~~~~~~~~~~~~~~~~~ |
82 | 82 | ||
83 | No variables have been deprecated in this release. | 83 | - ``CVE_CHECK_IGNORE`` should be replaced with :term:`CVE_STATUS` |
84 | |||
84 | 85 | ||
85 | .. _migration-5.0-removed-variables: | 86 | .. _migration-5.0-removed-variables: |
86 | 87 | ||
@@ -89,13 +90,14 @@ Removed variables | |||
89 | 90 | ||
90 | The following variables have been removed: | 91 | The following variables have been removed: |
91 | 92 | ||
92 | - ``DEPLOY_DIR_TAR``. | 93 | - ``DEPLOY_DIR_TAR``: no longer needed since the package_tar class was removed in 4.2. |
93 | - ``PYTHON_PN``: Python 2 has been removed, leaving Python 3 as the sole | 94 | - ``PYTHON_PN``: Python 2 has previously been removed, leaving Python 3 as the sole |
94 | major version. Therefore, an abstraction to differentiate both versions is | 95 | major version. Therefore, this abstraction to differentiate both versions is |
95 | no longer needed. | 96 | no longer needed. |
96 | - ``oldincludedir``. | 97 | - ``oldincludedir`` |
97 | - ``USE_L10N``: previously deprecated, and now removed. | 98 | - ``USE_L10N``: previously deprecated, and now removed. |
98 | - ``CVE_SOCKET_TIMEOUT``. | 99 | - ``CVE_SOCKET_TIMEOUT`` |
100 | - ``SERIAL_CONSOLES_CHECK`` - use :term:`SERIAL_CONSOLES` instead as all consoles specified in the latter are checked for their existence before a ``getty`` is started. | ||
99 | 101 | ||
100 | .. _migration-5.0-removed-recipes: | 102 | .. _migration-5.0-removed-recipes: |
101 | 103 | ||
@@ -105,9 +107,10 @@ Removed recipes | |||
105 | The following recipes have been removed in this release: | 107 | The following recipes have been removed in this release: |
106 | 108 | ||
107 | - ``libcroco``: deprecated and archived by the Gnome Project. | 109 | - ``libcroco``: deprecated and archived by the Gnome Project. |
110 | - ``liberror-perl``: unmaintained and no longer needed - moved to meta-perl. | ||
108 | - ``linux-yocto``: version 6.1 (version 6.6 provided instead). | 111 | - ``linux-yocto``: version 6.1 (version 6.6 provided instead). |
109 | - ``zvariant``: fails to build with newer Rust. | ||
110 | - ``systemtap-uprobes``: obsolete. | 112 | - ``systemtap-uprobes``: obsolete. |
113 | - ``zvariant``: fails to build with newer Rust. | ||
111 | 114 | ||
112 | .. _migration-5.0-removed-classes: | 115 | .. _migration-5.0-removed-classes: |
113 | 116 | ||
@@ -125,10 +128,75 @@ In ``tune-core2``, the cpu models ``n270`` and ``core2duo`` are no longer | |||
125 | passed to QEMU, since its documentation recommends not using them with ``-cpu`` | 128 | passed to QEMU, since its documentation recommends not using them with ``-cpu`` |
126 | option. Therefore, from now on, ``Nehalem`` model is used instead. | 129 | option. Therefore, from now on, ``Nehalem`` model is used instead. |
127 | 130 | ||
131 | |||
132 | ipk packaging changes | ||
133 | ~~~~~~~~~~~~~~~~~~~~~ | ||
134 | |||
135 | ipk packaging (using ``opkg``) now uses ``zstd`` compression instead of ``xz`` | ||
136 | for better compression and performance. This does mean that ``.ipk`` packages | ||
137 | built using the 5.0 release requires Opkg built with zstd enabled --- naturally | ||
138 | this is the case in 5.0, but at least by default these packages will not be | ||
139 | usable on older systems where Opkg does not have zstd enabled at build time. | ||
140 | |||
141 | Additionally, the internal dependency solver in Opkg is now deprecated --- it | ||
142 | is still available in this release but will trigger a warning if selected. | ||
143 | The default has been the external ``libsolv`` solver for some time, but if you | ||
144 | have explicitly removed that from :term:`PACKAGECONFIG` for Opkg to | ||
145 | select the internal solver, you should plan to switch to ``libsolv`` in the | ||
146 | near future (by including ``libsolv`` your custom :term:`PACKAGECONFIG` value | ||
147 | for Opkg, or reverting to the default value). | ||
148 | |||
149 | |||
150 | motd message when using ``DISTRO = "poky"`` | ||
151 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
152 | |||
153 | The default ``poky`` :term:`DISTRO` is explicitly a *reference* distribution | ||
154 | for testing and development purposes. It enables most hardware and software | ||
155 | features so that they can be tested, but this also means that | ||
156 | from a security point of view the attack surface is very large. | ||
157 | |||
158 | We encourage anyone using the Yocto Project for production use to create | ||
159 | their own distribution and not use Poky. To encourage this behaviour | ||
160 | further, in 5.0 a warning has been added to ``/etc/motd`` when Poky is used | ||
161 | so that the developer will see it when they log in. If you are creating your | ||
162 | own distribution this message will not show up. | ||
163 | |||
164 | For information on how to create your own distribution, see | ||
165 | ":ref:`dev-manual/custom-distribution:creating your own distribution`". | ||
166 | |||
128 | .. _migration-5.0-misc-changes: | 167 | .. _migration-5.0-misc-changes: |
129 | 168 | ||
130 | Miscellaneous changes | 169 | Miscellaneous changes |
131 | ~~~~~~~~~~~~~~~~~~~~~ | 170 | ~~~~~~~~~~~~~~~~~~~~~ |
132 | 171 | ||
133 | - ``bitbake-whatchanged`` script was removed. | 172 | - ``bitbake-whatchanged`` script was removed as it was broken and unmaintained. |
173 | |||
174 | - ``scripts/sstate-cache-management.sh`` has been replaced by | ||
175 | ``scripts/sstate-cache-management.py``, a more performant Python-based version. | ||
176 | |||
177 | - The ``bmap-tools`` recipe has been renamed to ``bmaptool``. | ||
178 | |||
179 | - ``gpgme`` has had Python binding support disabled since upstream does not | ||
180 | support Python 3.12 yet. This will be fixed in future once it is fixed upstream.) | ||
181 | |||
182 | - A warning will now be shown if the ``virtual/`` prefix is used in runtime | ||
183 | contexts (:term:`RDEPENDS` / :term:`RPROVIDES`) --- | ||
184 | See :ref:`virtual-slash <qa-check-virtual-slash>` for details. | ||
185 | |||
186 | - ``recipetool`` now prefixes the names of recipes created for Python modules | ||
187 | with ``python3-``. | ||
188 | |||
189 | - The :ref:`ref-classes-cve-check` class no longer produces a warning for | ||
190 | remote patches --- it only logs a note and does not try to fetch the patch | ||
191 | in order to scan it for issues or CVE numbers. However, CVE number | ||
192 | references in remote patch file names will now be picked up. | ||
193 | |||
194 | - The values of :term:`PE` and :term:`PR` have been dropped from | ||
195 | ``-f{file,macro,debug}-prefix-map``, in order to avoid unnecessary churn | ||
196 | in debugging symbol paths when the version is bumped. This is unlikely to | ||
197 | cause issues, but if you are paying attention to the debugging source path | ||
198 | (e.g. in recipes that need to manipulate these files during packaging) then | ||
199 | you will notice the difference. A new :term:`TARGET_DBGSRC_DIR` variable is | ||
200 | provided to make this easier. | ||
201 | |||
134 | - ``ccache`` no longer supports FORTRAN. | 202 | - ``ccache`` no longer supports FORTRAN. |