Hi,
I'm in the process of moving our image generation from ELBE to Isar - and of course
I'm running into unforseen situations ;-)
ELBE relies on apt-repositories where already build packages are stored, ready for
installation on the target, therefore we have all our custom stuff already build and
available as Debian packages and I surely do not want to rebuild these packages in
Isar.
So, I added an extra layer and appended a sources list file to DISTRO_APT_SOURCES,
pointing to our local apt-repository (aptly) and added one of our locally hosted
packages to IMAGE_INSTALL. This somewhat naive approach backfired immediatetly
when trying to build an image:
ERROR: Nothing PROVIDES 'XXXX' (but mc:qemuarm64-trixie:/home/isar/isar-image/isar/meta-isar/recipes-core/images/
isar-image-base.bb DEPENDS on or otherwise requires it
where XXXX is the locally hosted package name.
This is probably expected behaviour, I assume. What would be the best way to tackle that?
Overwriting the part of the Isar-bootstrapping where the package lists are build?
Defining another list of packages to be installed after bootstrapping is complete?
I'd like to avoid adding recipies for every local package,
thanks in advance for every suggestion,
Uli