From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Otavio Salvador : systemd.bbclass: depends on systemd
Date: Fri, 03 Feb 2012 18:34:44 -0800 [thread overview]
Message-ID: <4F2C9944.9050402@linux.intel.com> (raw)
In-Reply-To: <20120204021817.GB26306@sakrah.homelinux.org>
On 03/02/12 18:18, Khem Raj wrote:
> On (04/02/12 03:00), Andreas Müller wrote:
>>>> Which recipes really depend on systemd during build? I know about
>>>> polkit, something else?
>
> why not make it a globally selectable ?
> so we can make sure that autoconf does not try to guess
> but we tell it if systemd features should {en|dis}abled
> explicitly and something like virtual/init-manager or something
> since I think it has to coexist with sysvinit or upstart
> whatever one chooses.
We should definitely do this, I've not had enough time to figure out. I
think it's going to have to be a distro level thing as so far as I can
tell we need to be able to:
o set the init system
o include certain packages
o potentially enable/disable configure flags
I've not had much opportunity to look into this yet but we need to be
certain whichever mechanism we enable works for systemd, sysvinit,
upstart, s6, whatever.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-02-04 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120201080441.DA76610333@opal>
2012-02-03 13:14 ` [oe-commits] Otavio Salvador : systemd.bbclass: depends on systemd Martin Jansa
2012-02-03 15:30 ` Otavio Salvador
2012-02-03 15:47 ` Martin Jansa
2012-02-03 16:58 ` Otavio Salvador
2012-02-04 0:15 ` Andrea Adami
2012-02-04 0:31 ` Koen Kooi
2012-02-04 2:00 ` Andreas Müller
2012-02-04 2:15 ` Peter Bigot
2012-02-04 2:25 ` Khem Raj
2012-02-04 7:58 ` Martin Jansa
2012-02-04 2:18 ` Khem Raj
2012-02-04 2:34 ` Joshua Lock [this message]
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=4F2C9944.9050402@linux.intel.com \
--to=josh@linux.intel.com \
--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.