[PATCH 0/2] Rework deployment of image artifacts

["'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>]

As the changing of the DEPLOY_DIR_IMAGE has proven to be fundamentally
incompatible with custom initrd recipes, this patch was reverted,
re-introducing the do_copy_boot_files error on DTBs that are named
equally but belong to different mc targets.

This series mitigate the issue by keeping the layout of DEPLOY_DIR_IMAGE,
but prefixing the DTB_FILES with PN and DISTRO. These prefixes are
then stripped again during imaging.

Note, that the series has been CI tested against the "dtbdeploy" and "dev"
tags.

Best regards,
Felix Moessbauer
Siemens AG

Felix Moessbauer (2):
  Revert "meta: Deploy image build artifacts into distro- and
    image-specific subdirs"
  prefix DTB files with PN in deploy dir

 RECIPE-API-CHANGELOG.md                       | 84 +++----------------
 .../installer-add-rootfs.bbclass              |  9 +-
 meta/classes-recipe/image.bbclass             | 17 ++--
 .../imagetypes_container.bbclass              |  2 +-
 meta/classes-recipe/imagetypes_wic.bbclass    |  2 +-
 meta/conf/bitbake.conf                        |  3 +-
 .../wic/plugins/source/bootimg-efi-isar.py    |  3 +-
 .../plugins/source/isoimage-isohybrid-isar.py |  2 +-
 testsuite/cibase.py                           |  2 +-
 testsuite/citest.py                           |  7 +-
 testsuite/start_vm.py                         |  2 +-
 11 files changed, 36 insertions(+), 97 deletions(-)

-- 
2.53.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260410132250.3320171-1-felix.moessbauer%40siemens.com.