[oe] [meta-oe 6/7] systemd.bbclass: automatically extend FILES_* for systemd packages

[Otavio Salvador]

On Tue, Feb 14, 2012 at 10:42, Andreas Müller
<schnitzeltony at googlemail.com>wrote:

> Currently I am testing the automatic parsing for different recipes.
> Following the 'After=' and 'WantedBy=' works fine but before sending
> out I would like to get some comments on the following
> assumptions/questions:
>
> * There is no need for recipes to install links for 'WantedBy' entries
> since systemd-systemctl-native takes care. E.G the code in
> lightttpd_1.4.30.bbappend for this can be removed (it works on the
> wrong paths anyway) -> there is no need for systemd.bbclass to follow
> 'WantedBy'. Correct?
>

Links ought to be kept to be handled by systemd-systemctl-native.


> * For dropbear_2011.54.bbappend, the automatic parsing leaves
> dropbear at .service and dropbear.service ( link to /dev/null ) unpacked.
> In dropbear.socket there is 'Conflicts=dropbear.service'. Shall the
> algorithm follow also services linked by Conflicts= and pack those
> service files?
>

The /dev/null link is to force disable the init script. This is difficult
to do automatically so for now I'd say to do it byhand.


> * dropbear_2011.54.bbappend: Is dropbear at .service a candidate for a
> second *-systemd packet?
>

No; The @ is to allow multiple instance. Look at
http://www.freedesktop.org/software/systemd/man/systemd.unit.html


> * are there other keys which might need follow-up too?
>

Not that I am aware of at this moment.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br