Hi,

I'm trying to model building different images for different machines -
but for the same architecture. That promises the reuse of common
packages when everything is modeled properly (the kernel, e.g., will be
configured to enable that). But it also exposes some ugliness.

These are my targets so far:

multiconfig:machine1-distro:image
multiconfig:machine2-distro:image

Both machines will share DISTRO_ARCH but will have different MACHINE
variables, obviously. The image recipe will be widely identical, except
for some machine-specific packages, selected by "package-${MACHINE}". So
far so good.

But now we have the same image target in the same distro-arch work
folder, and that clashes. To resolve that, I also need change PN in the
image recipe to "image-${MACHINE}", and that results in the following
targets:

multiconfig:machine1-distro:image-machine1
multiconfig:machine2-distro:image-machine1

Kind of ugly, having the machine ID twice in this target specification.
Is there any better way to model such a scenario?

Thanks,
Jan