From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: systemd packages -> image
Date: Thu, 10 Nov 2011 10:35:12 +0000 [thread overview]
Message-ID: <1627207.pd1HnObREr@helios> (raw)
In-Reply-To: <j9g8hi$43b$1@dough.gmane.org>
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.
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...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-10 10:41 UTC|newest]
Thread overview: 9+ 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 [this message]
2011-11-25 13:14 ` Steffen Sledz
2011-11-10 11:05 ` Anders Darander
-- strict thread matches above, loose matches on Subject: below --
2011-11-09 22:15 Andreas Müller
2011-11-09 22:20 ` Andreas Müller
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=1627207.pd1HnObREr@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.