From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: systemd packages -> image
Date: Thu, 10 Nov 2011 11:20:34 +0100 [thread overview]
Message-ID: <j9g8hi$43b$1@dough.gmane.org> (raw)
In-Reply-To: <2977361.KIYvSC26hZ@helios>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 10-11-11 10:47, Paul Eggleton schreef:
> On Thursday 10 November 2011 08:47:17 Anders Darander wrote:
>> * Andreas Müller <schnitzeltony@gmx.de> [111109 23:17]:
>>> Imagine a recipe is included into an image by a task and later gets
>>> systemd- native support. How about forcing the packages in
>>> SYSTEMD_PACKAGES packed into images in case
>>>
>>> IMAGE_INIT_MANAGER = "systemd"
>>>
>>> is found in the image definition?
>>
>> Sure, that sounds like a nice idea. Although, in that case, SysV-init
>> files should probably also be packaged in separate packages and be
>> installed in a similar manner.
>
> Why are we going to such an effort to provide both sysvinit and systemd
> in the same distro? Why not make it a distro policy decision? This would
> save a huge amount of work.
So I can start sending patches to add the systemd files to ${PN} in oe-core
recipes now? That's the big hold up: lack of vision from the OE-core folks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFOu6VyMkyGM64RGpERAsQzAKCiZU39orO0DUQ7sUw6y5Dk/pbk9ACggabc
BcceXFVsVOS2GqnFvC2KbZ4=
=MYbw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-10 10:27 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 [this message]
2011-11-10 10:35 ` Paul Eggleton
2011-11-25 13:14 ` Steffen Sledz
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='j9g8hi$43b$1@dough.gmane.org' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox