Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: paul.eggleton@linux.intel.com, alexander.kanevskiy@intel.com
Subject: [PATCH 0/4] extend buildhistory
Date: Wed, 25 Nov 2015 10:30:28 +0100	[thread overview]
Message-ID: <cover.1448442869.git.patrick.ohly@intel.com> (raw)

The initial implementation of YOCTO #8138
("buildhistory-extra.bbclass: store more information about a build")
had some issues ("kconfig" file not preserved) but more importantly,
additional changes are needed to support also gathering information
about native recipes.

I am proposing to include only the "buildhistory.bbclass: support
extending the content of the build history" patch into OE-core.

The original buildhistory-extra.bbclass and the modifications made to
it are included here merely to provide the context for that change and
to publish the modifications.

The following changes since commit d0f3f3a294d509560bd12b93b26eeec65cfee314:

  package_manager.py: Delete installed_pkgs.txt file (2015-11-24 15:55:33 +0000)

are available in the git repository at:

  git://github.com/pohly/openembedded-core buildhistory-extra
  https://github.com/pohly/openembedded-core/tree/buildhistory-extra

Ismo Puustinen (1):
  buildhistory-extra.bbclass: simplify usage

Patrick Ohly (2):
  buildhistory.bbclass: support extending the content of the build
    history
  buildhistory-extra.bbclass: more complete and reliable data gathering

Paul Eggleton (1):
  buildhistory-extra.bbclass: store more information about a build

 meta/classes/buildhistory-extra.bbclass | 127 ++++++++++++++++++++++++++++++++
 meta/classes/buildhistory.bbclass       |  13 +++-
 2 files changed, 139 insertions(+), 1 deletion(-)
 create mode 100644 meta/classes/buildhistory-extra.bbclass

-- 
2.1.4



             reply	other threads:[~2015-11-25  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  9:30 Patrick Ohly [this message]
2015-11-25  9:30 ` [PATCH 1/4] buildhistory-extra.bbclass: store more information about a build Patrick Ohly
2015-11-25  9:30 ` [PATCH 2/4] buildhistory.bbclass: support extending the content of the build history Patrick Ohly
2015-11-27  0:25   ` Paul Eggleton
2015-11-25  9:30 ` [PATCH 3/4] buildhistory-extra.bbclass: simplify usage Patrick Ohly
2015-11-25  9:30 ` [PATCH 4/4] buildhistory-extra.bbclass: more complete and reliable data gathering Patrick Ohly
2015-11-27  0:38   ` Paul Eggleton
2015-11-27  0:34 ` [PATCH 0/4] extend buildhistory Paul Eggleton
2015-11-27  8:36   ` Martin Jansa
2015-12-01 19:36   ` 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.1448442869.git.patrick.ohly@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=alexander.kanevskiy@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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