From: Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?= <antti.kaijanmaki@canonical.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] Allow users to specify dbus name replacement behaviour.
Date: Fri, 04 Apr 2014 03:00:56 +0300 [thread overview]
Message-ID: <533DF638.5070503@canonical.com> (raw)
In-Reply-To: <533DD568.9080807@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
On 04.04.2014 00:40, Denis Kenzior wrote:
> Hi Antti,
>>
>> Indeed, and this combined with commit 5f765259 one can easily run a
>> series of tests (let's say dialer UI, messaging..) with different
>> phonesim configurations changing the number of modems and phonesim .xml
>> files for each modem.
>
> I see what you needed that commit for now. While I can kind of see your
> usecase, I really wonder whether simply creating a large phonesim.conf
> and grouping modems there would be a less intrusive way to get what you
> want.
That previous commit is something that is useful if ofonod with phonesim
is ran with unpriviledged uid on top of a private system bus, which is
totally doable, and works in situations where you have to test let's say
a low level binding library which expects ofono to be found on the
system bus.
Our original idea was to run all of our tests on top of private system
and session buses and in this situation the environment variable to
change the phonesim configuration file location would have been all we
need (and anyway, I personally don't like hardcoded configuration file
paths;)
But we ran into trouble trying to run the whole unity8 stack on top of
private session and system buses (mainly getting all the necessary
services on both the system and session bus to run on there as well was
exploding the test setup complexity) so we though about another
solutions and figured out that keeping the rest of the system running as
is and only replacing ofonod instance on real system-bus would be pretty
straight forward technically (such small patches:). Jussi sent the
patches to the mailing list so that we could get your opinion on them
and turns out (thanks Marcel!) that there might be better solutions
available.
-- Antti
next prev parent reply other threads:[~2014-04-04 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 13:56 [PATCH 1/2] Allow users to specify dbus name replacement behaviour jussi.pakkanen
2014-04-02 13:56 ` [PATCH 2/2] Can set name replacement with command line arguments jussi.pakkanen
2014-04-02 18:39 ` [PATCH 1/2] Allow users to specify dbus name replacement behaviour Marcel Holtmann
2014-04-03 7:38 ` Jussi Pakkanen
2014-04-03 9:41 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-03 17:55 ` Marcel Holtmann
2014-04-03 23:45 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-04 0:09 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-04 0:13 ` Denis Kenzior
2014-04-04 0:11 ` Denis Kenzior
2014-04-04 0:50 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-03 21:40 ` Denis Kenzior
2014-04-04 0:00 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?= [this message]
2014-04-04 0:22 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-04 0:25 ` Denis Kenzior
2014-04-04 1:16 ` Antti =?unknown-8bit?q?Kaijanm=C3=A4ki?=
2014-04-03 17:50 ` Marcel Holtmann
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=533DF638.5070503@canonical.com \
--to=antti.kaijanmaki@canonical.com \
--cc=ofono@ofono.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.