From: Martin Jansa <martin.jansa@gmail.com>
To: "Iorga, Cristian" <cristian.iorga@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] connman: upgrade to 1.10
Date: Thu, 10 Jan 2013 20:00:12 +0100 [thread overview]
Message-ID: <20130110190012.GI3722@jama.palm1.palmone.com> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB161DCAA5@IRSMSX102.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Thu, Jan 10, 2013 at 06:47:26PM +0000, Iorga, Cristian wrote:
> Hello all,
> In SIGGEN_EXCLUDERECIPES_ABISAFE only connman-conf needs to be added, or connman + connman-conf? (see my V2 patch for connman 1.10 upgrade)
connman-conf only, V2 looks better
Cheers,
>
> Regards,
> Cristian
>
> -----Original Message-----
> From: Martin Jansa [mailto:martin.jansa@gmail.com]
> Sent: Thursday, January 10, 2013 10:58 AM
> To: Burton, Ross
> Cc: Iorga, Cristian; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] connman: upgrade to 1.10
>
> On Thu, Jan 10, 2013 at 07:56:30AM +0000, Ross Burton wrote:
> > On Thursday, 10 January 2013 at 07:15, Iorga, Cristian wrote:
> > > Well, I have the prior art stand by me.
> > > The same technique is applied for netbase.
> > >
> > > And, in this specific case, connman should be machine specific.
> > > Can you please give me more detail?
> > >
> > > The configuration file will have only the interface blacklist enabled in case of a qemu* machine.
> > netbase is a lot smaller than connman.
>
> and also listed in SIGGEN_EXCLUDERECIPES_ABISAFE
>
> >With this change you're rebuilding connman per-machine instead of sharing the package between compatible machines, with the only difference being a configuration file.
>
> And rebuilding also all stuff depending on connman.
>
> Cheers,
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-01-10 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:11 [PATCH] connman: upgrade to 1.10 Cristian Iorga
2013-01-09 17:42 ` Burton, Ross
2013-01-10 7:15 ` Iorga, Cristian
2013-01-10 7:56 ` Ross Burton
2013-01-10 8:19 ` Iorga, Cristian
2013-01-10 8:57 ` Martin Jansa
2013-01-10 18:47 ` Iorga, Cristian
2013-01-10 19:00 ` Martin Jansa [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=20130110190012.GI3722@jama.palm1.palmone.com \
--to=martin.jansa@gmail.com \
--cc=cristian.iorga@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox