Hi Alex,
Am Mittwoch, dem 18.10.2023 um 12:09 +0200 schrieb Alexander Kanavin:
> On Wed, 18 Oct 2023 at 11:57, Enrico Jörns <e...@pengutronix.de> wrote:
> > it's not really that it's 'forced' into all image. The .bbappend just says:
> >
> > > require ${@bb.utils.contains('DISTRO_FEATURES', 'rauc',
> > > '${BPN}_rauc.inc', '', d)}
> > The assumption was that if you have 'rauc' in you DISTRO_FEATURES, you want
> > to install it.
> > And this was just the best way I saw to automatically end up in base images
> > for this case while
> > ensuring that we do not modify the base packagegroup unconditionally.
>
> You should provide a packagegroup-rauc recipe, a sample rauc-image
> recipe (or set of recipes) that uses that packagegroup, and leave it
> at that. Users of meta-rauc will figure out the rest, particularly
> when and how they want to install rauc. You've just seen a specific
> case where it is *not* wanted in some images.
>
> Forcing your way into base packagegroups from oe-core via bbappends is
> really not the right way to go about things.
In how is this different to the default packagegroup handling in oe-core where
package 'force
themself' into images based on specific DISTRO_FEATURE or MACHINE_FEATURE
settings?
Thus this is a mechanism that is explicitly designed to be used by oe-core
exclusively?
Regards, Enrico
> Alex
>
--
Pengutronix e.K. | Enrico Jörns |
Embedded Linux Consulting & Support | https://www.pengutronix.de/ |
Steuerwalder Str. 21 | Phone: +49-5121-206917-180 |
31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61394): https://lists.yoctoproject.org/g/yocto/message/61394
Mute This Topic: https://lists.yoctoproject.org/mt/102035396/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
