On Sun, Jan 28, 2024 at 7:59 PM Alexander Kanavin
wrote:
> That said, if the difference between distros is only in specific
> recipe settings, then I think the builds will reuse each other's
> sstate, other than the recipes that differ, and their consumers.
>
Except for example when e.g. icecc i
That said, if the difference between distros is only in specific
recipe settings, then I think the builds will reuse each other's
sstate, other than the recipes that differ, and their consumers.
Alex
On Sun, 28 Jan 2024 at 13:48, Alexander Kanavin via
lists.yoctoproject.org
wrote:
>
> There's no
There's no way around this: you can't build the same recipe in two
different ways for two different images in the same DISTRO. The
different behavior has to be specified through config files and picked
up at runtime, and not through build time settings. All products and
builds and CI infrastructure
Thanks for your reply. It helps, but I see some issues with the
ROOTFS_POSTPROCESS_COMMAND.
For the config file this is a possible solution. But what can I do if I need
code changes? SSH announced they'll disable DSA support by default in a few
months and for all other images except one I would
Putting image specific tweaks into local.conf is not a good practice.
Local.conf should be extremely minimal, and ideally contain only
MACHINE and DISTRO.
I would do it with two different image recipes that share almost
everything via common .inc, except ROOTFS_POSTPROCESS_COMMAND. You can
find ex
[I posted this question on Stackoverflow:
https://stackoverflow.com/q/77871008/8452187]
I have two images with the same distro and the same machine and each image
should contain the same package, but build with different settings.
For example, the config file sshd_config is part of the opensshd
