All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex DAMIAN <alexandru.damian@intel.com>
To: bitbake-devel@lists.openembedded.org, richard.purdie@linuxfoundation.org
Cc: Alexandru DAMIAN <alexandru.damian@intel.com>
Subject: [PATCH 0/7] Adding Bitbake support for WebHob
Date: Wed, 18 Sep 2013 13:15:37 +0100	[thread overview]
Message-ID: <cover.1379505533.git.alexandru.damian@intel.com> (raw)

From: Alexandru DAMIAN <alexandru.damian@intel.com>


This is a set of patches that prepare Bitbake to support WebHob.

Among the significant changes:

* The extra_caches mechanism is replaced with a CookerFeature mechanism
that allows the UI clients to specify what features they need at connection time.
This allows the server to start, for example, with a minimum set of caches,
and load any additional caches on demand when the clients connect.

* Another CookerFeature is added that will make the server send the 
dependency tree to the clients, on request, when the server is ready to 
start processing the runqueue.

* There is a new server command that returns the contents of the data store.

* The data read from the the recipecache depends on what extra caches
have been loaded, and it's discovered at runtime instead of hardcoding.


The following changes since commit eaf06bc2840cc39026033de0779858b1bf82f06f:

  bitbake: cooker: return a copy checkPackages (2013-09-18 08:41:55 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib adamian/bitbake-core-changes-1809-2
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=adamian/bitbake-core-changes-1809-2

Alexandru DAMIAN (7):
  bitbake: cooker,xmlrpc,servers: implement CookerFeatures
  bitbake: cooker,runqueue: send the task dependency tree
  bitbake: build, runqueue: adds info to the *runQueue* events
  bitbake: cooker: get extra information from recipe cache
  bitbake: cooker, command: add a command to return global data
  bitbake: event: adding generic event for metadata usage
  bitbake: runqueue: add task hash to Queue events

 bitbake/bin/bitbake                      |  25 ++------
 bitbake/lib/bb/build.py                  |   2 +
 bitbake/lib/bb/cache_extra.py            |   6 ++
 bitbake/lib/bb/command.py                |   9 +++
 bitbake/lib/bb/cooker.py                 | 102 ++++++++++++++++++++++++-------
 bitbake/lib/bb/cookerdata.py             |   1 -
 bitbake/lib/bb/event.py                  |  10 +++
 bitbake/lib/bb/runqueue.py               |  20 ++++++
 bitbake/lib/bb/server/__init__.py        |   2 +-
 bitbake/lib/bb/server/process.py         |  23 +++++--
 bitbake/lib/bb/server/xmlrpc.py          |  29 ++++++---
 bitbake/lib/bb/ui/crumbs/hoblistmodel.py |   2 +-
 bitbake/lib/bb/ui/hob.py                 |   2 +-
 bitbake/lib/bb/ui/knotty.py              |   4 ++
 bitbake/lib/bb/ui/uievent.py             |   7 ++-
 15 files changed, 183 insertions(+), 61 deletions(-)

-- 
1.8.1.2



             reply	other threads:[~2013-09-18 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 12:15 Alex DAMIAN [this message]
2013-09-18 12:15 ` [PATCH 1/7] bitbake: cooker, xmlrpc, servers: implement CookerFeatures Alex DAMIAN
2013-09-18 12:15 ` [PATCH 2/7] bitbake: cooker, runqueue: send the task dependency tree Alex DAMIAN
2013-09-18 12:15 ` [PATCH 3/7] bitbake: build, runqueue: adds info to the *runQueue* events Alex DAMIAN
2013-09-18 12:15 ` [PATCH 4/7] bitbake: cooker: get extra information from recipe cache Alex DAMIAN
2013-09-18 12:15 ` [PATCH 5/7] bitbake: cooker, command: add a command to return global data Alex DAMIAN
2013-09-18 12:15 ` [PATCH 6/7] bitbake: event: adding generic event for metadata usage Alex DAMIAN
2013-09-18 12:15 ` [PATCH 7/7] bitbake: runqueue: add task hash to Queue events Alex DAMIAN

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=cover.1379505533.git.alexandru.damian@intel.com \
    --to=alexandru.damian@intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.