diff options
| -rw-r--r-- | documentation/migration-guides/migration-4.3.rst | 25 |
1 files changed, 15 insertions, 10 deletions
diff --git a/documentation/migration-guides/migration-4.3.rst b/documentation/migration-guides/migration-4.3.rst index d2c3d2ad98..17ea4e7127 100644 --- a/documentation/migration-guides/migration-4.3.rst +++ b/documentation/migration-guides/migration-4.3.rst | |||
| @@ -34,9 +34,9 @@ Layername override implications | |||
| 34 | Code can now know which layer a recipe is coming from through the newly added | 34 | Code can now know which layer a recipe is coming from through the newly added |
| 35 | :term:`FILE_LAYERNAME` variable and the ``layer-<layername> override``. This is being used | 35 | :term:`FILE_LAYERNAME` variable and the ``layer-<layername> override``. This is being used |
| 36 | for enabling QA checks on a per layer basis. For existing code this has the | 36 | for enabling QA checks on a per layer basis. For existing code this has the |
| 37 | side effect that the QA checks will apply to things being bbappended to recipes | 37 | side effect that the QA checks will apply to recipes being bbappended |
| 38 | from other layers. Those other layers would need to have patch upstream status | 38 | from other layers - for example, patches added through such bbappends will now |
| 39 | entries for patches being bbappended for example. | 39 | need to have the "Upstream-Status" specified in the patch header. |
| 40 | 40 | ||
| 41 | .. _migration-4.3-compiling-changes: | 41 | .. _migration-4.3-compiling-changes: |
| 42 | 42 | ||
| @@ -71,10 +71,13 @@ See :ref:`all supported distributions <system-requirements-supported-distros>`. | |||
| 71 | 71 | ||
| 72 | .. _migration-4.3-removed-machines: | 72 | .. _migration-4.3-removed-machines: |
| 73 | 73 | ||
| 74 | Removed machines | 74 | edgerouter machine removed |
| 75 | ~~~~~~~~~~~~~~~~ | 75 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 76 | 76 | ||
| 77 | The ``edgerouter`` BSP in ``meta-yocto-bsp`` has been removed. | 77 | The ``edgerouter`` reference BSP for the MIPS architecture in ``meta-yocto-bsp`` |
| 78 | has been removed as the hardware has been unavailable for some time. There is no | ||
| 79 | suitable reference MIPS hardware to replace it with, but the MIPS architecture | ||
| 80 | will continue to get coverage via QEMU build/boot testing. | ||
| 78 | 81 | ||
| 79 | .. _migration-4.3-go-changes: | 82 | .. _migration-4.3-go-changes: |
| 80 | 83 | ||
| @@ -86,7 +89,7 @@ Go language changes | |||
| 86 | 89 | ||
| 87 | .. _migration-4.3-systemd-changes: | 90 | .. _migration-4.3-systemd-changes: |
| 88 | 91 | ||
| 89 | Systemd changes | 92 | systemd changes |
| 90 | ~~~~~~~~~~~~~~~ | 93 | ~~~~~~~~~~~~~~~ |
| 91 | 94 | ||
| 92 | Upstream systemd is now more strict on filesystem layout and the ``usrmerge`` | 95 | Upstream systemd is now more strict on filesystem layout and the ``usrmerge`` |
| @@ -120,8 +123,8 @@ The following variables have been removed: | |||
| 120 | - ``AUTHOR`` | 123 | - ``AUTHOR`` |
| 121 | - ``PERLARCH`` | 124 | - ``PERLARCH`` |
| 122 | - ``PERLVERSION`` | 125 | - ``PERLVERSION`` |
| 123 | - ``QEMU_USE_SLIRP`` | 126 | - ``QEMU_USE_SLIRP`` - add ``slirp`` to ``TEST_RUNQEMUPARAMS`` instead. |
| 124 | - ``SERIAL_CONSOLES_CHECK``, which is no longer necessary because all | 127 | - ``SERIAL_CONSOLES_CHECK`` - no longer necessary because all |
| 125 | consoles listed in :term:`SERIAL_CONSOLES` are checked for their existence | 128 | consoles listed in :term:`SERIAL_CONSOLES` are checked for their existence |
| 126 | before a ``getty`` is started. | 129 | before a ``getty`` is started. |
| 127 | 130 | ||
| @@ -168,5 +171,7 @@ Miscellaneous changes | |||
| 168 | ``virtual/XXX`` provider/dependencies where a ``PREFIX`` was used as well, | 171 | ``virtual/XXX`` provider/dependencies where a ``PREFIX`` was used as well, |
| 169 | as we don't need both and it made automated dependency rewriting | 172 | as we don't need both and it made automated dependency rewriting |
| 170 | unnecessarily complex. In general this only affects internal toolchain | 173 | unnecessarily complex. In general this only affects internal toolchain |
| 171 | dependencies so isn't end user visible. | 174 | dependencies so isn't end user visible, but if for some reason you have |
| 175 | custom classes or recipes that rely upon the old providers then you will | ||
| 176 | need to update those. | ||
| 172 | 177 | ||
