Motivation for this patch series is sstate-cache reuse.
Basically we have dozen of products with several
different systemd configurations.
Problem is that there are many recipes which depend on systemd.
(or their packaging depends on it)
Especially qtwebengine which takes hours to build and created
sstate objects have several hundereds of gigabytes.
So instead of:
PACKAGECONFIG:remove:pn-systemd = " timesyncd"
we would like to do just:
BAD_RECOMMENDATIONS += "systemd-timesyncd"
That allows reuse of sstate-cache for such recipes because
it will build identically, just install to rootfs differently.
One alternative we considered was via systemd-conf, but binaries still
occupy space in rootfs which is not desirable for some devices:
ln -sf /dev/null ${D}${sysconfdir}/systemd/system/systemd-timesyncd.service
Please comment if you think that we should take a different
approach which is more in line with Yocto project best practices.
Peter Marko (3):
systemd: split timesyncd to its own package
systemd.bbclass: add non-recursive service packaging
systemd: split networkd to its own package
documentation/ref-manual/variables.rst | 10 ++++
meta/classes-recipe/systemd.bbclass | 15 ++---
meta/recipes-core/systemd/systemd_252.4.bb | 64 ++++++++++++++++++++--
3 files changed, 78 insertions(+), 11 deletions(-)
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176839):
https://lists.openembedded.org/g/openembedded-core/message/176839
Mute This Topic: https://lists.openembedded.org/mt/96825676/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
