All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] connman: enable connman client
Date: Sat, 23 Feb 2013 12:43:09 +0000	[thread overview]
Message-ID: <5128B95D.5070305@communistcode.co.uk> (raw)
In-Reply-To: <3284634.41HXpyBOqa@helios>

On 02/23/13 11:30, Paul Eggleton wrote:
> On Saturday 23 February 2013 09:02:07 Jack Mitchell wrote:
>> On 02/23/13 08:34, Ross Burton wrote:
>>> Also the fact that you have to do this is depressing.  I wonder why
>>> upstream doesn't want to install any of the tools?
>> Connmanctl is a helper, even though I have connman in my image, I
>> wouldn't want connmanctl. I assume this is why they don't ship it by
>> default; as my use case is fairly normal for connman.
> I would have thought if you had asked for the client to be built (or not asked
> for it not to be built, as the case may be) then surely you would want it
> installed (as far as make install goes anyway)?

Yes I misread, I thought we were explicity enabling it. I'll try to send 
an email off to upstream and see what they think.

>
>> Which leads to the next point, this should be a seperate package.
> Probably should be I think yes.

If no one beats me to it I'll look into this at work next week. Some of 
the tools should be split into packages too and I think there may be 
some distro specific tweaks also (e.g. wifi enabled etc).

>
> Cheers,
> Paul
>




  reply	other threads:[~2013-02-23 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 20:10 [PATCH] connman: enable connman client Cristian Iorga
2013-02-23  8:34 ` Ross Burton
2013-02-23  9:02   ` Jack Mitchell
2013-02-23 11:30     ` Paul Eggleton
2013-02-23 12:43       ` Jack Mitchell [this message]
2013-02-25  7:18   ` Iorga, Cristian
2013-02-25  8:21     ` Burton, Ross
2013-02-25  7:36   ` Iorga, Cristian

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=5128B95D.5070305@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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.