diff options
author | Paul Barker <pbarker@konsulko.com> | 2021-01-19 16:26:07 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-01-20 22:46:18 +0000 |
commit | 7a2545013cfed710011ab470ed30422e79622dca (patch) | |
tree | 49b727be627305fc28a78c9ac33dc7d39d0b4534 /scripts/buildhistory-diff | |
parent | 4e6cb084f53bff1ef2d8dab6eb5a4f0e73eed018 (diff) | |
download | poky-7a2545013cfed710011ab470ed30422e79622dca.tar.gz |
image_types_wic: Move wic working directory
By default the wic working directory is placed under the output
directory. When invoking wic under bitbake, the wic output directory is
added to PSEUDO_PATHS_IGNORE to avoid issues with files being removed
from outside a pseudo environment (see oe-core commit ad8f5532ff).
However, wic will copy the rootfs directory into its working directory
if it needs to add or remove content before creating a filesystem image.
This copy of the rootfs directory must be tracked by pseudo in order to
keep the permissions correct in the resulting image. So we can't have
the wic working directory under a path in PSEUDO_PATHS_IGNORE unless
we like broken permissions.
To fix this the new '-w' argument to wic is used to move the working
directory away from the output directory.
Note that wic deletes the temporary working directory automatically
when it finishes creating an image so users won't normally see the
'tmp-wic' directory under WORKDIR.
Fixes [Yocto #14129]
(From OE-Core rev: 4d07169499c47fa9dc759e6f81843416a6dc25c5)
Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/buildhistory-diff')
0 files changed, 0 insertions, 0 deletions