From: Radu Moisan <radu.moisan@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/28][RFC] systemd Integration
Date: Thu, 03 Jan 2013 10:03:52 +0200 [thread overview]
Message-ID: <50E53B68.6020505@intel.com> (raw)
In-Reply-To: <4078626.EH4CM1sFWo@helios>
On 01/01/2013 12:10 AM, Paul Eggleton wrote:
> On Friday 28 December 2012 16:24:36 Radu Moisan wrote:
>> On 12/25/2012 03:13 AM, Saul Wold wrote:
>>> Also, you do not provide very clear information at the beginning, but
>>> I assume to enable systemd, it's just setting DISTRO_FEATURE +=
>>> "systemd", or is there more?
>> DISTRO_FEATURES_INITMAN = "systemd" it's all you need. DISTRO_FEATURE +=
>> "systemd" might also work in some extent since I'm checking against
>> DISTRO_FEATURES, however there are variables like
>> VIRTUAL_RUNTIME_init_manager (which is inherited legacy) which get set
>> from DISTRO_FEATURES_INITMAN. The way to go is with DISTRO_FEATURES_INITMAN.
> Can you explain why we need another variable for this?
Initially I went for VIRTUAL-RUNTIME_init_manager, but Richard suggested
I should get rid of lower case ambiguity and he proposed
DISTRO_FEATURES_INITMAN.
Radu
next prev parent reply other threads:[~2013-01-03 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 17:11 [PATCH 00/28][RFC] systemd Integration Radu Moisan
2012-12-20 22:03 ` Saul Wold
2012-12-21 9:35 ` Radu Moisan
2012-12-21 12:15 ` Burton, Ross
2012-12-22 0:43 ` Otavio Salvador
2012-12-22 17:01 ` Ross Burton
2012-12-21 17:24 ` Otavio Salvador
2012-12-21 11:31 ` Burton, Ross
2012-12-21 17:36 ` Saul Wold
2012-12-25 1:13 ` Saul Wold
2012-12-28 14:24 ` Radu Moisan
2012-12-31 22:10 ` Paul Eggleton
2013-01-03 8:03 ` Radu Moisan [this message]
2013-01-03 8:16 ` Radu Moisan
2013-01-03 17:23 ` Saul Wold
2013-01-04 15:45 ` Radu Moisan
2013-01-04 15:48 ` Radu Moisan
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=50E53B68.6020505@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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