From: <Mikko.Rapeli@bmw.de>
To: <jacob.kroon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH 2/2] buildhistory: support generating md5sum of files
Date: Tue, 8 Jan 2019 10:32:32 +0000 [thread overview]
Message-ID: <20190108103232.GS7349@hiutale> (raw)
In-Reply-To: <CAPbeDCm=0X_8cN6_WCexaLBNcYrVv3zT_27g8uXW_eh-iGc=TA@mail.gmail.com>
On Mon, Jan 07, 2019 at 03:17:00PM +0100, Jacob Kroon wrote:
> On Sun, Jan 6, 2019 at 7:14 PM Jacob Kroon <jacob.kroon@gmail.com> wrote:
> >
> > Introduce 'md5' in BUILDHISTORY_FEATURES and enable it by default
> > when doing reproducible builds.
> >
> > When enabled this will additionally create:
> >
> > files-in-package-md5.txt
> > files-in-image-md5.txt
> > files-in-sdk-md5.txt
> >
> > containing the md5 checksums of regular files.
> >
> > Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
> > ---
> > meta/classes/buildhistory.bbclass | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
> > index 33eb1b00f6..00f0701dec 100644
> > --- a/meta/classes/buildhistory.bbclass
> > +++ b/meta/classes/buildhistory.bbclass
> > @@ -7,7 +7,8 @@
> > # Copyright (C) 2007-2011 Koen Kooi <koen@openembedded.org>
> > #
> >
> > -BUILDHISTORY_FEATURES ?= "image package sdk"
> > +BUILDHISTORY_FEATURES ?= "image package sdk \
> > + ${@ "md5" if bb.utils.to_boolean(d.getVar('BUILD_REPRODUCIBLE_BINARIES')) else ""}"
> > BUILDHISTORY_DIR ?= "${TOPDIR}/buildhistory"
> > BUILDHISTORY_DIR_IMAGE = "${BUILDHISTORY_DIR}/images/${MACHINE_ARCH}/${TCLIBC}/${IMAGE_BASENAME}"
> > BUILDHISTORY_DIR_PACKAGE = "${BUILDHISTORY_DIR}/packages/${MULTIMACH_TARGET_SYS}/${PN}"
> > @@ -526,7 +527,12 @@ buildhistory_list_files() {
> > eval ${FAKEROOTENV} ${FAKEROOTCMD} $find_cmd
> > else
> > eval $find_cmd
> > - fi | sort -k5 | sed 's/ * -> $//' > $2 )
> > + fi | sort -k5 | sed 's/ * -> $//' > $2
> > + if [ "${@bb.utils.contains('BUILDHISTORY_FEATURES', 'md5', '1', '0', d)}" = "1" ] ; then
> > + md5filename=$(echo $2 | sed 's/\.txt$/-md5.txt/')
> > + find -type f | xargs -I{} -n1 md5sum {} | sort -k2 > $md5filename
> > + [ -s $md5filename ] || rm $md5filename # remove result if empty
>
> I added this remove because I thought it didn't make sense to keep
> empty files around, but I now realize that the "files-in-package.txt"
> file is kept around, even if empty. Is there a preference on what to
> do here ?
FWIW, I'm wiping the all buildhistory data with external scripts before doing a
clean build. Basically a "git rm -rf *" in buildhistory directory. Otherwise
stale data about images, packages etc which are no longer built remain in
buildhistory.
-Mikko
next prev parent reply other threads:[~2019-01-08 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 18:13 [RFC][PATCH 1/2] buildhistory: simplify buildhistory_list_files() Jacob Kroon
2019-01-06 18:13 ` [RFC][PATCH 2/2] buildhistory: support generating md5sum of files Jacob Kroon
2019-01-06 23:08 ` André Draszik
2019-01-07 9:38 ` Jacob Kroon
2019-01-07 14:31 ` Richard Purdie
2019-01-07 15:50 ` Jacob Kroon
2019-01-07 14:17 ` Jacob Kroon
2019-01-08 10:32 ` Mikko.Rapeli [this message]
2019-01-08 10:36 ` Jacob Kroon
2019-01-08 11:02 ` Mikko.Rapeli
2019-01-09 11:20 ` Peter Kjellerstedt
2019-01-09 18:36 ` Jacob Kroon
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=20190108103232.GS7349@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=jacob.kroon@gmail.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