From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: systemd packages -> image
Date: Fri, 25 Nov 2011 14:14:09 +0100 [thread overview]
Message-ID: <4ECF94A1.9050803@dresearch-fe.de> (raw)
In-Reply-To: <1627207.pd1HnObREr@helios>
On 10.11.2011 11:35, Paul Eggleton wrote:
> On Thursday 10 November 2011 11:20:34 Koen Kooi wrote:
>> So I can start sending patches to add the systemd files to ${PN} in oe-core
>> recipes now?
>
> I would think if these additions are conditional upon systemd being in
> DISTRO_FEATURES, I can't see a problem. I think the ideal situation would be
> to have a generic "init" bbclass (or some better name) which does all the work
> for you regardless of whether sysvinit or systemd is used (i.e. it would
> effectively replace update-rc.d.bbclass), and save having to have packaging
> boilerplate in every recipe.
What about upstart in this context? An generic "init" bbclass should support this too.
> My main point was, yes there are both people who want to stay with sysvinit
> and people who are keen to move to systemd, but I'm not convinced both of
> those need to be catered for within the same distro policy.
>
>> That's the big hold up: lack of vision from the OE-core folks.
>
> This is a community project, if you have ideas or suggestions, just start the
> discussion...
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@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
next prev parent reply other threads:[~2011-11-25 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 22:21 systemd packages -> image Andreas Müller
2011-11-10 7:47 ` Anders Darander
2011-11-10 9:47 ` Paul Eggleton
2011-11-10 10:20 ` Koen Kooi
2011-11-10 10:35 ` Paul Eggleton
2011-11-25 13:14 ` Steffen Sledz [this message]
2011-11-10 11:05 ` Anders Darander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECF94A1.9050803@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox