public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9] devtool / recipetool fixes
Date: Tue,  6 Sep 2016 22:03:21 +1200	[thread overview]
Message-ID: <cover.1473155977.git.paul.eggleton@linux.intel.com> (raw)

Very late for M3 I know, but here are some fixes for issues I found
recently in devtool / recipetool as well as support for creating
recipes to package node.js code without using npm.


The following changes since commit 55bb6816aca39bfa25d4f7e2158a57a5f0ac1cca:

  oeqa.buildperf: correct globalres time format (2016-09-06 10:24:00 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/devtool20-oe
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/devtool20-oe

Paul Eggleton (9):
  lib/oe/patch: handle non-UTF8 encoding when reading patches
  devtool: update-recipe: support files with subdir=
  recipetool: create: AX_PKG_SWIG should add dependency on swig-native
  recipetool: create: fix mapping python dependencies to python-dbg package
  recipetool: create: support git submodules
  recipetool: create: add --keep-temp command line option
  recipetool: create: allow license variable handling to be rerun
  recipetool: create: support node.js code outside of npm
  recipetool: create: avoid extra blank lines in output recipe

 meta/classes/npm.bbclass                         |   4 +
 meta/lib/oe/patch.py                             |  28 +++--
 meta/lib/oe/recipeutils.py                       |  12 ++-
 scripts/lib/devtool/standard.py                  |  38 ++++++-
 scripts/lib/recipetool/create.py                 | 129 +++++++++++++----------
 scripts/lib/recipetool/create_buildsys.py        |   2 +-
 scripts/lib/recipetool/create_buildsys_python.py |   4 +
 scripts/lib/recipetool/create_npm.py             | 111 ++++++++++++++++++-
 8 files changed, 258 insertions(+), 70 deletions(-)

-- 
2.5.5



             reply	other threads:[~2016-09-06 10:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 10:03 Paul Eggleton [this message]
2016-09-06 10:03 ` [PATCH 1/9] lib/oe/patch: handle non-UTF8 encoding when reading patches Paul Eggleton
2016-09-06 15:50   ` Enrico Scholz
2016-09-06 20:16     ` Paul Eggleton
2016-09-07 10:07       ` Enrico Scholz
2016-09-06 10:03 ` [PATCH 2/9] devtool: update-recipe: support files with subdir= Paul Eggleton
2016-09-06 10:03 ` [PATCH 3/9] recipetool: create: AX_PKG_SWIG should add dependency on swig-native Paul Eggleton
2016-09-06 10:03 ` [PATCH 4/9] recipetool: create: fix mapping python dependencies to python-dbg package Paul Eggleton
2016-09-06 10:03 ` [PATCH 5/9] recipetool: create: support git submodules Paul Eggleton
2016-09-07  6:23   ` Ola x Nilsson
2016-09-07 21:07     ` Paul Eggleton
2016-09-06 10:03 ` [PATCH 6/9] recipetool: create: add --keep-temp command line option Paul Eggleton
2016-09-06 10:03 ` [PATCH 7/9] recipetool: create: allow license variable handling to be rerun Paul Eggleton
2016-09-06 10:03 ` [PATCH 8/9] recipetool: create: support node.js code outside of npm Paul Eggleton
2016-09-06 10:03 ` [PATCH 9/9] recipetool: create: avoid extra blank lines in output recipe 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.1473155977.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.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