Re: systemd services in the rootfs

[Florin Sarbu <florin.sarbu@windriver.com>]

So choosing, for example ${PN} to hold the systemd services, and also 
choose to use sysvinit as the init manager, then I'd end up with a 
rootfs containing useless systemd services.
Then can someone detail what is SYSTEMD_PACKAGES used for? If it's only 
for adding the packages to PACKAGES, then it doesn't make too much sense 
to exist in my opinion, as it would just be an extra variable defined to 
do something that can be achieved without defining a extra variable.

Florin

On 02/14/2013 12:17 PM, Burton, Ross wrote:
> On 14 February 2013 09:09, Florin Sarbu <florin.sarbu@windriver.com> wrote:
>> The issue I was referring to was that the individual packages (that contain
>> the systemd service files) generated from various recipes, do not end up in
>> the rootfs solely by having them declared in the SYSTEMD_PACKAGES and having
>> DISTRO_FEATURES_INITMAN ="systemd". You need now to explicitly add these
>> ${PN}-systemd (or whatever name you choose for the packages that will hold
>> the systemd services) in some packagegroups or image recipes to have them in
>> the rootfs. It is not a question of where to have them in the rootfs, but
>> rather to have them added in the do_rootfs stage.
> Put the service files into the relevant package (i.e. $PN, instead of
> into a separate package of their own.
>
> This is different to how meta-systemd worked, because in oe-core
> systemd is a DISTRO_FEATURE and not something you can decide at image
> construction time.
>
> Ross