Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Keroulas <patrick.keroulas@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 4/4] ring-daemon: new package
Date: Mon, 25 Apr 2016 17:20:32 -0400 (EDT)	[thread overview]
Message-ID: <1359905598.420554.1461619232368.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20160425212434.10734123@free-electrons.com>


On Apr 25, 2016, at 3:24 PM, Thomas Petazzoni thomas.petazzoni at free-electrons.com wrote:
 
> On Mon, 25 Apr 2016 14:18:42 -0400 (EDT), Patrick Keroulas wrote:
> 
>> Concerning the D-Bus daemon, Ring relies on a session bus but D-Bus
>> initscript starts a daemon for system bus only. I can change D-Bus
>> initscript instead of starting it from our Ring initscript. In this
>> case, in which package should I add the patch? ring-daemon or dbus?
> 
> I *think* it should be handled in the DBus package itself, though I am
> not entirely sure. As I understand it, a "session bus" is typically
> associated to one particular user when this user logs into the system,
> right? How does that work for ring? Does it use a session bus running
> as the "ring" user? Aren't session buses normally used for "real" users?

That's right. Ring is mainly intended to be used by real users logged
on a desktop or a mobile platform. However, we'd like to port it to 
embedded platforms to cover a larger usage (m2m, video capture, door 
bell...). And this is why a fake 'ring' user has to be created and the
D-Bus session address has to be exported.

Is it possible to patch a package (dbus) "from" another one (ring-daemon)?

Regards,

Patrick

      reply	other threads:[~2016-04-25 21:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 20:57 [Buildroot] [PATCH v1 0/4] Patrick Keroulas
2016-04-22 20:57 ` [Buildroot] [PATCH v1 1/4] libpjsip: add gnutls support and fix various things Patrick Keroulas
2016-04-22 21:21   ` Thomas Petazzoni
2016-05-03 21:08     ` Patrick Keroulas
2016-05-03 21:43       ` Arnout Vandecappelle
2016-05-04 15:22         ` Patrick Keroulas
2016-05-04 19:23           ` Arnout Vandecappelle
2016-04-22 20:57 ` [Buildroot] [PATCH v1 2/4] msgpack: bump to version 1.4.0 Patrick Keroulas
2016-04-22 21:23   ` Thomas Petazzoni
2016-05-02 20:57     ` Patrick Keroulas
2016-04-22 21:52   ` Thomas Petazzoni
2016-04-22 20:57 ` [Buildroot] [PATCH v1 3/4] openDHT: new package Patrick Keroulas
2016-04-22 21:30   ` Thomas Petazzoni
2016-04-22 20:57 ` [Buildroot] [PATCH v1 4/4] ring-daemon: " Patrick Keroulas
2016-04-22 22:19   ` Thomas Petazzoni
2016-04-25 14:29     ` Jérôme Oufella
2016-04-25 18:18     ` Patrick Keroulas
2016-04-25 19:24       ` Thomas Petazzoni
2016-04-25 21:20         ` Patrick Keroulas [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=1359905598.420554.1461619232368.JavaMail.zimbra@savoirfairelinux.com \
    --to=patrick.keroulas@savoirfairelinux.com \
    --cc=buildroot@busybox.net \
    /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