From: Andrew Shadura <andrew.shadura@collabora.co.uk>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] dbus: add user sessions support
Date: Tue, 24 Nov 2015 15:07:58 +0100 [thread overview]
Message-ID: <56546F3E.1010409@collabora.co.uk> (raw)
In-Reply-To: <CAJTo0LYHDtBX6SaQvaOe61Fwwbcw=o4wubQ3s5wDa9ds7dD6bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On 24/11/15 15:03, Burton, Ross wrote:
> On 20 November 2015 at 14:38, Andrew Shadura
> <andrew.shadura@collabora.co.uk> wrote:
>
>> Enable the user-sessions support with a PACKAGECONFIG flag.
>
> What is the impact on this if someone is using systemd but doesn't want
> user sessions? Should we enable it if the DISTRO_FEATURES contains
> systemd by default?
It is okay to use systemd and not use user sessions. Possibly, we want
to enable it by default in the future, but it should be okay to have it
disabled for now unless it's switched on from elsewhere.
--
Cheers,
Andrew
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-11-24 14:08 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2015-12-07 19:08 ` Andrew Shadura
2016-02-02 17:04 [PATCH 1/2] dbus: use ${systemd_system_unitdir} Andrew Shadura
2016-02-02 17:06 ` [PATCH 2/2] dbus: add user sessions support 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=56546F3E.1010409@collabora.co.uk \
--to=andrew.shadura@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 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.