Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 00/10] Support progress reporting
Date: Mon, 13 Jun 2016 14:52:16 +1200	[thread overview]
Message-ID: <cover.1465786269.git.paul.eggleton@linux.intel.com> (raw)

Add code to support progress reporting within OpenEmbedded, as well as a
couple of related changes to allow reworking the extensible SDK
installation process.


The following changes since commit 6d1379c8818400e5cdc442e6142f08a110fd5b95:

  lib/bb/main.py: Fix use of BBPOSTCONF and BBPRECONF (2016-06-09 18:00:45 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib paule/startup-bb
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/startup-bb

Paul Eggleton (10):
  knotty: provide a symlink to the latest console log
  knotty: import latest python-progressbar
  lib: implement basic task progress support
  lib/bb/progress: add MultiStageProgressReporter
  fetch2: implement progress support
  knotty: add code to support showing progress for sstate object querying
  knotty: show task progress bar
  knotty: add quiet output mode
  runqueue: add ability to enforce that tasks are setscened
  runqueue: report progress for "Preparing RunQueue" step

 lib/bb/build.py                |  34 ++++
 lib/bb/event.py                |  27 +++
 lib/bb/fetch2/__init__.py      |   4 +-
 lib/bb/fetch2/git.py           |  52 +++++-
 lib/bb/fetch2/wget.py          |  26 ++-
 lib/bb/main.py                 |   9 +
 lib/bb/msg.py                  |   5 +-
 lib/bb/progress.py             | 266 ++++++++++++++++++++++++++++
 lib/bb/runqueue.py             | 131 +++++++++++++-
 lib/bb/ui/knotty.py            | 143 ++++++++++++---
 lib/bb/ui/uihelper.py          |   7 +-
 lib/progressbar.py             | 384 ----------------------------------------
 lib/progressbar/LICENSE.txt    |  52 ++++++
 lib/progressbar/__init__.py    |  49 ++++++
 lib/progressbar/compat.py      |  44 +++++
 lib/progressbar/progressbar.py | 315 +++++++++++++++++++++++++++++++++
 lib/progressbar/widgets.py     | 391 +++++++++++++++++++++++++++++++++++++++++
 17 files changed, 1519 insertions(+), 420 deletions(-)
 create mode 100644 lib/bb/progress.py
 delete mode 100644 lib/progressbar.py
 create mode 100644 lib/progressbar/LICENSE.txt
 create mode 100644 lib/progressbar/__init__.py
 create mode 100644 lib/progressbar/compat.py
 create mode 100644 lib/progressbar/progressbar.py
 create mode 100644 lib/progressbar/widgets.py

-- 
2.5.5



             reply	other threads:[~2016-06-13  2:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  2:52 Paul Eggleton [this message]
2016-06-13  2:52 ` [PATCH 01/10] knotty: provide a symlink to the latest console log Paul Eggleton
2016-06-13  2:52 ` [PATCH 02/10] knotty: import latest python-progressbar Paul Eggleton
2016-06-13  2:52 ` [PATCH 03/10] lib: implement basic task progress support Paul Eggleton
2016-06-13  2:52 ` [PATCH 04/10] lib/bb/progress: add MultiStageProgressReporter Paul Eggleton
2016-06-13  2:52 ` [PATCH 05/10] fetch2: implement progress support Paul Eggleton
2016-06-28 10:23   ` Burton, Ross
2016-06-28 10:33     ` Paul Eggleton
2016-06-13  2:52 ` [PATCH 06/10] knotty: add code to support showing progress for sstate object querying Paul Eggleton
2016-06-13  2:52 ` [PATCH 07/10] knotty: show task progress bar Paul Eggleton
2016-06-13  2:52 ` [PATCH 08/10] knotty: add quiet output mode Paul Eggleton
2016-06-13  2:52 ` [PATCH 09/10] runqueue: add ability to enforce that tasks are setscened Paul Eggleton
2016-06-13  2:52 ` [PATCH 10/10] runqueue: report progress for "Preparing RunQueue" step Paul Eggleton
2016-06-13 11:09   ` Richard Purdie
2016-06-13 12:16     ` Paul Eggleton
2016-06-15 21:46       ` Richard Purdie
2016-06-15 21:49         ` Paul Eggleton

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.1465786269.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=bitbake-devel@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