On Mon, 31 Oct 2022 at 22:32, Peter Bergin <[email protected]> wrote: > Sure, I can do that. My aim for override those in a bbappend is just for > development purposes and nothing I plan to use in production or push in > public. My way of working when I realized this was to build latest > master of systemd that had a bunch of patches that I would like to test. > To do that I needed to change git repo to systemd.git. When tested I > plan to backport relevant patches that I need to add to current systemd > version in oe-core to my local layer until next systemd release. Then I > thought this could simplify things for more people. But I'm fine if this > is not accepted for upstream and I can work around that.
We had a related discussion recently regarding mesa, where there is a similar desire to 'reuse' the recipe from core as much as possible but build from a different revision. Typically this would be done by having some kind of common .inc file (systemd.inc in this case), and then adding the missing parts in a custom .bb that includes the .inc across layers (bitbake allows this). No promises about keeping things in .inc compatible with whatever happens in custom layers though. Another option is to use the devupstream class, and there are examples in oe-core for it. Would that work for you? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#172342): https://lists.openembedded.org/g/openembedded-core/message/172342 Mute This Topic: https://lists.openembedded.org/mt/94696056/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
