diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-09-23 17:20:26 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-10-07 10:54:25 +0100 |
commit | 9fece9c36125aeec1ee3b3845fc914ec0dbf3034 (patch) | |
tree | 9ee53e939349006219c1b325c5afa395e723dd14 /documentation/migration-guides/migration-3.2.rst | |
parent | 84251f8d24034163ec785d0f5715634b90f2c1bf (diff) | |
download | poky-9fece9c36125aeec1ee3b3845fc914ec0dbf3034.tar.gz |
manuals: add reference to the "do_install" task
[YOCTO #14508]
(From yocto-docs rev: 933ad27b81dfc4a28e7c48ca7bb2d1363e8c037f)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/migration-guides/migration-3.2.rst')
-rw-r--r-- | documentation/migration-guides/migration-3.2.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/migration-guides/migration-3.2.rst b/documentation/migration-guides/migration-3.2.rst index a4d0479d92..8d251deaf7 100644 --- a/documentation/migration-guides/migration-3.2.rst +++ b/documentation/migration-guides/migration-3.2.rst | |||
@@ -60,7 +60,7 @@ pseudo as the interprocess round trip to the server is avoided. | |||
60 | 60 | ||
61 | There is a possible complication where some existing recipe may break, for | 61 | There is a possible complication where some existing recipe may break, for |
62 | example, a recipe was found to be writing to ``${B}/install`` for | 62 | example, a recipe was found to be writing to ``${B}/install`` for |
63 | ``make install`` in ``do_install`` and since ``${B}`` is listed as not to be tracked, | 63 | ``make install`` in :ref:`ref-tasks-install` and since ``${B}`` is listed as not to be tracked, |
64 | there were errors trying to ``chown root`` for files in this location. Another | 64 | there were errors trying to ``chown root`` for files in this location. Another |
65 | example was the ``tcl`` recipe where the source directory :term:`S` is set to a | 65 | example was the ``tcl`` recipe where the source directory :term:`S` is set to a |
66 | subdirectory of the source tree but files were written out to the directory | 66 | subdirectory of the source tree but files were written out to the directory |
@@ -207,7 +207,7 @@ files into a subdirectory and reference that instead. | |||
207 | deploy class now cleans ``DEPLOYDIR`` before ``do_deploy`` | 207 | deploy class now cleans ``DEPLOYDIR`` before ``do_deploy`` |
208 | ---------------------------------------------------------- | 208 | ---------------------------------------------------------- |
209 | 209 | ||
210 | ``do_deploy`` as implemented in the :ref:`deploy <ref-classes-deploy>` class now cleans up ${:term:`DEPLOYDIR`} before running, just as ``do_install`` cleans up ${:term:`D`} before running. This reduces the risk of :term:`DEPLOYDIR` being accidentally contaminated by files from previous runs, possibly even with different config, in case of incremental builds. | 210 | ``do_deploy`` as implemented in the :ref:`deploy <ref-classes-deploy>` class now cleans up ${:term:`DEPLOYDIR`} before running, just as :ref:`ref-tasks-install` cleans up ${:term:`D`} before running. This reduces the risk of :term:`DEPLOYDIR` being accidentally contaminated by files from previous runs, possibly even with different config, in case of incremental builds. |
211 | 211 | ||
212 | Most recipes and classes that inherit the :ref:`deploy <ref-classes-deploy>` class or interact with ``do_deploy`` are unlikely to be affected by this unless they add ``prefuncs`` to ``do_deploy`` *which also* put files into ``${DEPLOYDIR}`` --- these should be refactored to use ``do_deploy_prepend`` instead. | 212 | Most recipes and classes that inherit the :ref:`deploy <ref-classes-deploy>` class or interact with ``do_deploy`` are unlikely to be affected by this unless they add ``prefuncs`` to ``do_deploy`` *which also* put files into ``${DEPLOYDIR}`` --- these should be refactored to use ``do_deploy_prepend`` instead. |
213 | 213 | ||