[oe] guidelines for upstart in oe?
Steffen Sledz
sledz at dresearch-fe.de
Fri Sep 16 15:29:48 UTC 2011
On 14.09.2011 17:31, Steffen Sledz wrote:
> If i remember right there are some first experiments with using upstart as an sysvinit replacement in some oe based distros.
>
> Do some guidelines or suggestions exist to make an application recipes upstart ready?
>
> Nowadays a recipe for a common service contains INITSCRIPT_NAME & Co and installs an init script for sysvinit.
>
> How should such a recipe be modified to be able to install the application in a native upstart image (without sysvinit compatible runlevels)?
Let me put it in concrete terms.
Is it possible to write a bb recipe in a way like this?
---------------------->snip<-------------------------
...
IF IMAGE USES UPSTART AS INIT THEN
inherit autotools
do_install_append() {
install -d ${D}${sysconfdir}/init
install -m 0644 ${S}/upstartscript ${D}${sysconfdir}/init/foo.conf
}
ELSE
inherit autotools update-rc.d
do_install_append() {
install -d ${D}${sysconfdir}/init.d
install -m 0755 ${WORKDIR}/initscript ${D}${sysconfdir}/init.d/foo
}
INITSCRIPT_NAME = "foo"
FI
...
---------------------->snip<-------------------------
Regards
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz at dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
More information about the Openembedded-devel
mailing list