From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] Implement file checksums
Date: Wed, 23 May 2012 00:23:30 +0100 [thread overview]
Message-ID: <cover.1337728949.git.paul.eggleton@linux.intel.com> (raw)
This is 2/3 of the changes required to implement local file checksums;
the other third is a patch to base.bbclass which will be sent to the
OE-Core list.
The following changes (against Poky, but apply cleanly against BitBake
master with -p2) are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/file-checksum-bb
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/file-checksum-bb
Paul Eggleton (2):
bitbake: refactor out codeparser cache into a separate class
bitbake: implement checksums for local files in SRC_URI
bitbake/lib/bb/cache.py | 129 ++++++++++++++++++++++++-
bitbake/lib/bb/checksum.py | 90 +++++++++++++++++
bitbake/lib/bb/codeparser.py | 191 +++++++++++--------------------------
bitbake/lib/bb/cooker.py | 2 +
bitbake/lib/bb/fetch2/__init__.py | 85 +++++++++++++++++
bitbake/lib/bb/siggen.py | 24 +++++
6 files changed, 382 insertions(+), 139 deletions(-)
create mode 100644 bitbake/lib/bb/checksum.py
--
1.7.9.5
next reply other threads:[~2012-05-22 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:23 Paul Eggleton [this message]
2012-05-22 23:23 ` [PATCH 1/2] bitbake: refactor out codeparser cache into a separate class Paul Eggleton
2012-05-22 23:23 ` [PATCH 2/2] bitbake: implement checksums for local files in SRC_URI Paul Eggleton
2012-05-22 23:45 ` Mark Hatle
2012-05-22 23:50 ` Paul Eggleton
2012-05-22 23:55 ` Paul Eggleton
2012-05-23 9:42 ` Richard Purdie
2012-05-23 10:25 ` [PATCH 0/2] Implement file checksums Richard Purdie
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.1337728949.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 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.