[OE-core] [PATCH] systemd: update version from 216 to 218

[Bottazzini, Bruno]

On Wed, 4 Feb 2015 12:48:35 +0100
Enrico Scholz <enrico.scholz at sigma-chemnitz.de> wrote:

> Bruno Bottazzini
> <bruno.bottazzini-ral2JQCrhuEAvxtiuMwx3w at public.gmane.org> writes:
> 
> > +PACKAGES =+ "${PN}-services-ask-password"
> > +SUMMARY_${PN}-services-ask-password = "systemd's service and tool
> > to query the user for a system password"
> > +RRECOMMENDS_${PN}-services-ask-password = "${PN}-services-base"
> > +FILES_${PN}-services-ask-password = "\
> > +        ${rootprefix}/bin/systemd-ask-password \
> > +        ${rootprefix}/bin/systemd-tty-ask-password-agent \
> > +
> > ${systemd_unitdir}/system/multi-user.target.wants/systemd-ask-password-wall.path
> > \
> > +
> > ${systemd_unitdir}/system/sysinit.target.wants/systemd-ask-password-console.path
> > \
> > +
> > ${systemd_unitdir}/system/systemd-ask-password-console.path \
> > +
> > ${systemd_unitdir}/system/systemd-ask-password-console.service \
> > +        ${systemd_unitdir}/system/systemd-ask-password-wall.path \
> > +
> > ${systemd_unitdir}/system/systemd-ask-password-wall.service \ +"
> 
> I think, enumerating services in this kind becomes a maintenance
> nightmare.  E.g. you have to check for every future systemd version
> whether service gets listed in a new .wants.  Using wildcards can
> simplify this; e.g. see systemd_elito_populate_packages() in
> 
>           https://www.cvg.de/people/ensc/systemd_216.bbappend
> 
> 
> Enrico

Enrico,

On your example, wouldn't we have to enumerate the packages too ? 
But now it is on a different place.

Where did you get this file ? I looked into master branch but I
couldn't find it.

Thanks,

Bruno Bottazzini