From: Patrick Ohly <patrick.ohly@intel.com>
To: Andrew Shadura <andrew.shadura@collabora.co.uk>
Cc: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] dbus: build with systemd support
Date: Mon, 07 Dec 2015 20:02:38 +0100 [thread overview]
Message-ID: <1449514958.30674.37.camel@intel.com> (raw)
In-Reply-To: <ef26757c2c56efbd37d8577432a8e451399ad245.1448030272.git.andrew.shadura@collabora.co.uk>
On Fri, 2015-11-20 at 15:38 +0100, Andrew Shadura wrote:
> It's good to have the extra functionality, such as seat support
> provided with systemd support. Not least of all to support
> systemd user-sessions.
Your patch is against D-Bus 1.10.2, which is not yet in OE-core master.
I adapted the patch to the current D-Bus 1.8.20, but there the
advantages turned out to be (IMHO) fairly minor: it only adds logging
via journald.
socket activation via systemd already works even without
--enable-systemd, because the recipe explicitly installs the systemd
unit files and the code itself supports it also without
--enable-systemd.
But I like your patches, so perhaps including D-Bus 1.10.x (1.10.6 is
the latest stable release) can be considered for the next OE-core
release?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2015-12-07 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:38 [PATCH 1/2] dbus: build with systemd support Andrew Shadura
2015-11-20 14:38 ` [PATCH 2/2] dbus: add user sessions support Andrew Shadura
2015-11-24 14:03 ` Burton, Ross
2015-11-24 14:07 ` Andrew Shadura
2016-01-08 14:44 ` Patrick Ohly
2015-11-20 16:09 ` [PATCH 1/2] dbus: build with systemd support Jussi Kukkonen
2015-11-20 16:12 ` Andrew Shadura
2015-12-07 19:02 ` Patrick Ohly [this message]
2015-12-07 19:08 ` Andrew Shadura
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=1449514958.30674.37.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=andrew.shadura@collabora.co.uk \
--cc=openembedded-core@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.