poky: reset subtree on master HEAD(a88251b3e7)
As part of the last subtree update, I used master-next as the
subtree basis because there was a fix we needed in order to get QEMU
to pass. I didn't realize that master-next deviated (because they use
to just have short-term patches in it). Reset the content to the same
fix but from the master branch.
Change-Id: Ic7d2f0ac42e9da3eb263586b26ba56d8798d5bcf
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
diff --git a/poky/documentation/ref-manual/classes.rst b/poky/documentation/ref-manual/classes.rst
index 1d01456..9520d0b 100644
--- a/poky/documentation/ref-manual/classes.rst
+++ b/poky/documentation/ref-manual/classes.rst
@@ -564,6 +564,13 @@
``CVE-ID.patch``, e.g. ``CVE-2019-20633.patch``, in the :term:`SRC_URI` and using
CVE metadata of format ``CVE: CVE-ID`` in the commit message of the patch file.
+.. note::
+
+ Commit message metadata (``CVE: CVE-ID`` in a patch header) will not be scanned
+ in any patches that are remote, i.e. that are anything other than local files
+ referenced via ``file://`` in SRC_URI. However, a ``CVE-ID`` in a remote patch
+ file name itself will be registered.
+
If the recipe adds ``CVE-ID`` as flag of the :term:`CVE_STATUS` variable with status
mapped to ``Ignored``, then the CVE state is reported as ``Ignored``::
@@ -1582,6 +1589,12 @@
This is only relevant when you are using runtime package management
on your target system.
+- ``virtual-slash:`` Checks to see if ``virtual/`` is being used in
+ :term:`RDEPENDS` or :term:`RPROVIDES`, which is not good practice ---
+ ``virtual/`` is a convention intended for use in the build context
+ (i.e. :term:`PROVIDES` and :term:`DEPENDS`) rather than the runtime
+ context.
+
- ``xorg-driver-abi:`` Checks that all packages containing Xorg
drivers have ABI dependencies. The ``xserver-xorg`` recipe provides
driver ABI names. All drivers should depend on the ABI versions that
@@ -2374,6 +2387,24 @@
Internally this uses the :ref:`ref-classes-python_pep517` class.
+.. _ref-classes-python_maturin:
+
+``python_maturin``
+==================
+
+The :ref:`ref-classes-python_maturin` class provides support for python-maturin, a replacement
+for setuptools_rust and another "backend" for building Python Wheels.
+
+.. _ref-classes-python_mesonpy:
+
+``python_mesonpy``
+==================
+
+The :ref:`ref-classes-python_mesonpy` class enables building Python modules which use the
+meson-python build system.
+
+Internally this uses the :ref:`ref-classes-python_pep517` class.
+
.. _ref-classes-python_pep517:
``python_pep517``
diff --git a/poky/documentation/ref-manual/qa-checks.rst b/poky/documentation/ref-manual/qa-checks.rst
index 58526a0..53b1836 100644
--- a/poky/documentation/ref-manual/qa-checks.rst
+++ b/poky/documentation/ref-manual/qa-checks.rst
@@ -799,6 +799,14 @@
section in the Yocto Project Development Tasks Manual. See also the
":ref:`ref-classes-ptest`" section.
+.. _qa-check-virtual-slash:
+
+- ``<variable> is set to <value> but the substring 'virtual/' holds no meaning in this context. It only works for build time dependencies, not runtime ones. It is suggested to use 'VIRTUAL-RUNTIME_' variables instead.``
+
+ ``virtual/`` is a convention intended for use in the build context
+ (i.e. :term:`PROVIDES` and :term:`DEPENDS`) rather than the runtime
+ context (i.e. :term:`RPROVIDES` and :term:`RDEPENDS`). Use
+ :term:`VIRTUAL-RUNTIME` variables instead for the latter.
Configuring and Disabling QA Checks
diff --git a/poky/documentation/ref-manual/variables.rst b/poky/documentation/ref-manual/variables.rst
index 0dc881e..9cdcc1b 100644
--- a/poky/documentation/ref-manual/variables.rst
+++ b/poky/documentation/ref-manual/variables.rst
@@ -4048,7 +4048,7 @@
The default value of the variable is set as follows in the
``meta/conf/distro/defaultsetup.conf`` file::
- INHERIT_DISTRO ?= "debian devshell sstate license"
+ INHERIT_DISTRO ?= "debian devshell sstate license remove-libtool create-spdx"
:term:`INHIBIT_DEFAULT_DEPS`
Prevents the default dependencies, namely the C compiler and standard
@@ -8813,6 +8813,10 @@
value so that executables built using the SDK also have the flags
applied.
+ :term:`TARGET_DBGSRC_DIR`
+ Specifies the target path to debug source files. The default is
+ ``/usr/src/debug/${PN}/${PV}``.
+
:term:`TARGET_FPU`
Specifies the method for handling FPU code. For FPU-less targets,
which include most ARM CPUs, the variable must be set to "soft". If