1Release 3.3 (hardknott) 2======================= 3 4This section provides migration information for moving to the Yocto 5Project 3.3 Release (codename "hardknott") from the prior release. 6 7 8.. _migration-3.3-minimum-system-requirements: 9 10Minimum system requirements 11--------------------------- 12 13You will now need at least Python 3.6 installed on your build host. Most recent 14distributions provide this, but should you be building on a distribution that 15does not have it, you can use the ``buildtools-tarball`` (easily installable 16using ``scripts/install-buildtools``) --- see 17:ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions` 18for details. 19 20.. _migration-3.3-removed-recipes: 21 22Removed recipes 23--------------- 24 25The following recipes have been removed: 26 27- ``go-dep``: obsolete with the advent of go modules 28- ``gst-validate``: replaced by ``gst-devtools`` 29- ``linux-yocto``: removed 5.8 version recipes (5.4 / 5.10 still provided) 30- ``vulkan-demos``: replaced by ``vulkan-samples`` 31 32 33.. _migration-3.3-common-license-only-versions: 34 35Single version common license file naming 36----------------------------------------- 37 38Some license files in ``meta/files/common-licenses`` have been renamed to match 39current SPDX naming conventions: 40 41- AGPL-3.0 -> AGPL-3.0-only 42- GPL-1.0 -> GPL-1.0-only 43- GPL-2.0 -> GPL-2.0-only 44- GPL-3.0 -> GPL-3.0-only 45- LGPL-2.0 -> LGPL-2.0-only 46- LGPL-2.1 -> LGPL-2.1-only 47- LGPL-3.0 -> LGPL-3.0-only 48 49Additionally, corresponding "-or-later" suffixed files have been added e.g. 50``GPL-2.0-or-later``. 51 52It is not required that you change :term:`LICENSE` values as there are mappings 53from the original names in place; however, in rare cases where you have a recipe 54which sets :term:`LIC_FILES_CHKSUM` to point to file(s) in 55``meta/files/common-licenses`` (which in any case is not recommended) you will 56need to update those. 57 58 59.. _migration-3.3-python3targetconfig: 60 61New ``python3targetconfig`` class 62--------------------------------- 63 64A new :ref:`python3targetconfig <ref-classes-python3targetconfig>` class has been 65created for situations where you would previously have inherited the 66:ref:`python3native <ref-classes-python3native>` class but need access to target configuration data (such as 67correct installation directories). Recipes where this situation applies should 68be changed to inherit ``python3targetconfig`` instead of ``python3native``. This 69also adds a dependency on target ``python3``, so it should only be used where 70appropriate in order to avoid unnecessarily lengthening builds. 71 72Some example recipes where this change has been made: ``gpgme``, ``libcap-ng``, 73``python3-pycairo``. 74 75 76.. _migration-3.3-distutils-path: 77 78``setup.py`` path for Python modules 79------------------------------------ 80 81In a Python module, sometimes ``setup.py`` can be buried deep in the 82source tree. Previously this was handled in recipes by setting :term:`S` to 83point to the subdirectory within the source where ``setup.py`` is located. 84However with the recent :ref:`pseudo <overview-manual/concepts:fakeroot and pseudo>` 85changes, some Python modules make changes to files beneath ``${S}``, for 86example:: 87 88 S = "${WORKDIR}/git/python/pythonmodule" 89 90then in ``setup.py`` it works with source code in a relative fashion, such 91as ``../../src``. This causes pseudo to fail as it isn't able to track 92the paths properly. This release introduces a new ``DISTUTILS_SETUP_PATH`` 93variable so that recipes can specify it explicitly, for example:: 94 95 S = "${WORKDIR}/git" 96 DISTUTILS_SETUP_PATH = "${S}/python/pythonmodule" 97 98Recipes that inherit from ``distutils3`` (or 99:ref:`setuptools3 <ref-classes-setuptools3>` which itself inherits 100``distutils3``) that also set :term:`S` to 101point to a Python module within a subdirectory in the aforementioned 102manner should be changed to set ``DISTUTILS_SETUP_PATH`` instead. 103 104 105.. _migration-3.3-bitbake: 106 107BitBake changes 108--------------- 109 110- BitBake is now configured to use a default ``umask`` of ``022`` for all tasks 111 (specified via a new :term:`BB_DEFAULT_UMASK` variable). If needed, ``umask`` can 112 still be set on a per-task basis via the ``umask`` varflag on the task 113 function, but that is unlikely to be necessary in most cases. 114 115- If a version specified in :term:`PREFERRED_VERSION` is not available this 116 will now trigger a warning instead of just a note, making such issues more 117 visible. 118 119 120.. _migration-3.3-packaging: 121 122Packaging changes 123----------------- 124 125The following packaging changes have been made; in all cases the main package 126still depends upon the split out packages so you should not need to do anything 127unless you want to take advantage of the improved granularity: 128 129- ``dbus``: ``-common`` and ``-tools`` split out 130- ``iproute2``: split ``ip`` binary to its own package 131- ``net-tools``: split ``mii-tool`` into its own package 132- ``procps``: split ``ps`` and ``sysctl`` into their own packages 133- ``rpm``: split build and extra functionality into separate packages 134- ``sudo``: split ``sudo`` binary into ``sudo-sudo`` and libs into ``sudo-lib`` 135- ``systemtap``: examples, Python scripts and runtime material split out 136- ``util-linux``: ``libuuid`` has been split out to its own 137 ``util-linux-libuuid`` recipe (and corresponding packages) to avoid circular 138 dependencies if ``libgcrypt`` support is enabled in ``util-linux``. 139 (``util-linux`` depends upon ``util-linux-libuuid``.) 140 141 142.. _migration-3.3-misc: 143 144Miscellaneous changes 145--------------------- 146 147- The default poky :term:`DISTRO_VERSION` value now uses the core metadata's 148 git hash (i.e. :term:`METADATA_REVISION`) rather than the date (i.e. 149 :term:`DATE`) to reduce one small source of non-reproducibility. You can 150 of course specify your own :term:`DISTRO_VERSION` value as desired 151 (particularly if you create your own custom distro configuration). 152- ``adwaita-icon-theme`` version 3.34.3 has been added back, and is selected 153 as the default via :term:`PREFERRED_VERSION` in 154 ``meta/conf/distro/include/default-versions.inc`` due to newer versions 155 not working well with ``librsvg`` 2.40. ``librsvg`` is not practically 156 upgradeable at the moment as it has been ported to Rust, and Rust is not 157 (yet) in OE-Core, but this will change in a future release. 158- ``ffmpeg`` is now configured to disable GPL-licensed portions by default 159 to make it harder to accidentally violate the GPL. To explicitly enable GPL 160 licensed portions, add ``gpl`` to :term:`PACKAGECONFIG` for ``ffmpeg`` 161 using a bbappend (or use ``PACKAGECONFIG_append_pn-ffmpeg = " gpl"`` in 162 your configuration.) 163- ``connman`` is now set to conflict with ``systemd-networkd`` as they 164 overlap functionally and may interfere with each other at runtime. 165- Canonical SPDX license names are now used in image license manifests in 166 order to avoid aliases of the same license from showing up together (e.g. 167 ``GPLv2`` and ``GPL-2.0``) 168