docs: migration-3.3 drop distutils labels, terms

The distutils* classes and DISUTILS* terms are no longer defined so
replace their usage with ``text``.

(From yocto-docs rev: c0e0e0b9416cb7a2fed3efe9d32ee905b6391f24)

Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Tim Orling
2022-03-01 08:36:17 -08:00
committed by Richard Purdie
parent 48e3604317
commit e2218a9684

View File

@@ -90,17 +90,17 @@ example::
then in ``setup.py`` it works with source code in a relative fashion, such
as ``../../src``. This causes pseudo to fail as it isn't able to track
the paths properly. This release introduces a new :term:`DISTUTILS_SETUP_PATH`
the paths properly. This release introduces a new ``DISTUTILS_SETUP_PATH``
variable so that recipes can specify it explicitly, for example::
S = "${WORKDIR}/git"
DISTUTILS_SETUP_PATH = "${S}/python/pythonmodule"
Recipes that inherit from :ref:`distutils3 <ref-classes-distutils3>` (or
Recipes that inherit from ``distutils3`` (or
:ref:`setuptools3 <ref-classes-setuptools3>` which itself inherits
:ref:`distutils3 <ref-classes-distutils3>`) that also set :term:`S` to
``distutils3``) that also set :term:`S` to
point to a Python module within a subdirectory in the aforementioned
manner should be changed to set :term:`DISTUTILS_SETUP_PATH` instead.
manner should be changed to set ``DISTUTILS_SETUP_PATH`` instead.
.. _migration-3.3-bitbake: