diff options
| author | Sven Roederer <devel-sven@geroedel.de> | 2021-05-07 21:35:20 +0200 |
|---|---|---|
| committer | Baptiste Jonglez <git@bitsofnetworks.org> | 2021-05-08 12:14:00 +0200 |
| commit | 6967903b01ea9f7c9f70d0185c3da276801dd78f (patch) | |
| tree | 384500de070e0ed7227a0ed9e96f7f6fc0d26eed /tools/tar/patches/110-symlink-force-permissions.patch | |
| parent | f990bddf6fb954bcbfc4fbcd54912e8d33800495 (diff) | |
| download | upstream-6967903b01ea9f7c9f70d0185c3da276801dd78f.tar.gz upstream-6967903b01ea9f7c9f70d0185c3da276801dd78f.tar.bz2 upstream-6967903b01ea9f7c9f70d0185c3da276801dd78f.zip | |
imagebuilder: unset BINARY_FOLDER and DOWNLOAD_FOLDER in final archive
Using these config-options to customize the folders used at build-time
makes these folder settings appear in generated archive. This causes the
imagebuilder to be not portable, as it's going to use the build-time folders
on the new systems. Errors look like:
mkdir: cannot create directory '/mnt/build': Permission denied
Makefile:116: recipe for target '_call_image' failed
make[2]: *** [_call_image] Error 1
Makefile:241: recipe for target 'image' failed
make[1]: *** [image] Error 2
The build-time settings of these folders are passed into the archives via
.config file.
The expected behavior is that after unpacking the imagebuilder acts like
these settings have their defaults, using intree folders. So unset the
build-time settings.
Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
Diffstat (limited to 'tools/tar/patches/110-symlink-force-permissions.patch')
0 files changed, 0 insertions, 0 deletions