On Thu, Dec 8, 2016 at 11:11 AM, Robert P. J. Day <[email protected]> wrote: > > almost certainly a dumb question, but what is the purpose of the > meta-openembedded/meta-systemd layer? i can see that the general > structure of that layer is a pile of bbappend files of the form: > > RPROVIDES_${PN} += "${PN}-systemd" > RREPLACES_${PN} += "${PN}-systemd" > RCONFLICTS_${PN} += "${PN}-systemd" > > so, in the case of, say, dropbear (which, from oe-core, is already a > systemd-controlled activity), i see a simple renaming of the package > produced. so instead of "dropbear", i'll get "dropbear-systemd". > > what am i missing? what is the purpose of that layer? > > rday > The initial systemd support was implemented in meta-systemd and later moved to oe-core. In the first implementation service files were packed in extra packages named ${PN}-systemd. This was undone when moving to oe-core. I think today meta-systemd is only there to keep package feeds happy.
Andreas -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
