Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/11] Change all bluez4 references to virtual/bluez
Date: Wed, 26 Mar 2014 16:35:24 +0100	[thread overview]
Message-ID: <20140326153524.GC3709@jama> (raw)
In-Reply-To: <CAP9ODKqkyfGzQROW=QZig2zvh-KrcyRFeKn9FtPndPUXWNDTUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On Wed, Mar 26, 2014 at 12:07:13PM -0300, Otavio Salvador wrote:
> Hello Martin,
> 
> On Wed, Mar 26, 2014 at 11:51 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Wed, Mar 26, 2014 at 09:27:54AM -0500, Lauren Post wrote:
> >> This group of patches support the change of hardcoded bluez4 to
> >> virtual/bluez so that the upgrade to bluez5 is easier.
> >>
> >> This group of patches must be applied together.  Bluez4 is still
> >> default provider but it will be easier to override and provide bluez5
> >> support in future.
> >>
> >> Note there is one related patch for openobex in meta-oe.
> >
> > virtual/* still doesn't work correctly in runtime variables, use
> > VIRTUAL-RUNTIME_bluez variable.
> ...
> 
> Those patches are for /depends/. Did I miss any runtime dependency here?

yes, in 11/11 4/11 2/11 and 1/11

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-03-26 15:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lauren.post@freescale.com>
2013-08-19 19:17 ` [v2][PATCH 1/2] directfb: Upgrade to 1.6.3 Lauren Post
2013-08-19 19:17   ` [v2][PATCH 2/2] directfb: add fusion patch for hangs on exit with Lauren Post
2013-08-20 22:54   ` [v2][PATCH 1/2] directfb: Upgrade to 1.6.3 Andre Draszik
2014-03-26 14:27 ` [PATCH 00/11] Change all bluez4 references to virtual/bluez Lauren Post
2014-03-26 14:27   ` [PATCH 01/11] bluez4: Add virtual/bluez as provider Lauren Post
2014-03-26 17:03     ` Burton, Ross
2014-03-26 17:26       ` Lauren Post
2014-03-26 14:27   ` [PATCH 02/11] conman: Change RDEPENDS on bluez4 to virtual/bluez Lauren Post
2014-03-26 14:27   ` [PATCH 03/11] libpcap: Change PACKAGECONFIG from bluez4 to virutal/bluez Lauren Post
2014-03-26 14:27   ` [PATCH 04/11] neard: Change RRECOMMENDS from bluez4 to virtual/bluez Lauren Post
2014-03-26 14:27   ` [PATCH 05/11] ofono: Change DEPENDS " Lauren Post
2014-03-26 14:28   ` [PATCH 06/11] pulseaudio: Change PACKAGECONFIG " Lauren Post
2014-03-26 15:30     ` Burton, Ross
2014-03-26 14:28   ` [PATCH 07/11] gst-plugin-bluetooth: Change DEPENDS " Lauren Post
2014-03-26 15:47     ` Burton, Ross
2014-03-26 14:28   ` [PATCH 08/11] gstreamer1.0-plugins-bad: Change PACKAGECONFIG " Lauren Post
2014-03-26 17:03     ` Burton, Ross
2014-03-26 14:28   ` [PATCH 09/11] bluez-hcidump: Change depends " Lauren Post
2014-03-26 16:19     ` Burton, Ross
2014-03-26 14:28   ` [PATCH 10/11] default-providers: Add virtual/bluez PROVIDER support to bluez4 Lauren Post
2014-03-26 17:00     ` Burton, Ross
2014-03-26 14:28   ` [PATCH 11/11] package-group: Change bluez4 to virtual/bluez Lauren Post
2014-03-26 14:51   ` [PATCH 00/11] Change all bluez4 references " Martin Jansa
2014-03-26 14:55     ` Lauren Post
2014-03-26 15:07     ` Otavio Salvador
2014-03-26 15:35       ` Martin Jansa [this message]
2014-03-26 16:18         ` Otavio Salvador
2014-03-26 15:40     ` Chris Larson
2014-03-26 16:33       ` Otavio Salvador
2014-03-26 16:51         ` Burton, Ross

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=20140326153524.GC3709@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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