From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [RFC PATCH 0/3] Reproducible build
Date: Wed, 23 May 2018 08:32:03 +0200 [thread overview]
Message-ID: <20180523063206.29180-1-claudius.heine.ext@siemens.com> (raw)
In-Reply-To: <3467a5ec-182e-8c9a-cd19-7ad898323be7@siemens.com>
From: Claudius Heine <ch@denx.de>
Hi,
this patchset contains a implementation of my proposed solution for
reproducible builds.
I am currenlty not quite sure if that is the right approach, but it is
the simplest I can think of currently.
As already described in my proposal, this patchset does the following:
1. Takes care that the package cache in the isar-bootstrap root file
system contains all the packages used for this distro/architecture.
2. A tarball is created after the package cache contains all the
packages needed by the image.
3. This tarball can be used as the basis of subsequent builds by
setting a bitbake variable.
This is just a first draft of this feature, maybe we can further improve
some steps and maybe there are better ideas to improve the usability.
Cheers,
Claudius
Claudius Heine (3):
meta/isar-bootstrap-helper+dpkg.bbclass: bind mount
/var/cache/apt/archives
meta/classes/image: added isar_bootstrap_tarball task
meta/isar-bootstrap: add 'do_restore_from_tarball' task
meta/classes/dpkg.bbclass | 5 ++++
meta/classes/image.bbclass | 10 +++++++
meta/classes/isar-bootstrap-helper.bbclass | 9 ++++++-
.../isar-bootstrap/isar-bootstrap.bb | 27 ++++++++++++++++++-
4 files changed, 49 insertions(+), 2 deletions(-)
--
2.17.0
next prev parent reply other threads:[~2018-05-23 6:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 11:55 Idea for implementing reproducible builds Claudius Heine
2018-05-22 13:47 ` Andreas Reichel
2018-05-22 14:24 ` Claudius Heine
2018-05-22 22:32 ` Baurzhan Ismagulov
2018-05-23 8:22 ` Claudius Heine
2018-05-23 11:34 ` Claudius Heine
2018-06-04 11:48 ` Baurzhan Ismagulov
2018-05-23 6:32 ` claudius.heine.ext [this message]
2018-05-23 6:32 ` [RFC PATCH 1/3] meta/isar-bootstrap-helper+dpkg.bbclass: bind mount /var/cache/apt/archives claudius.heine.ext
2018-05-23 6:32 ` [RFC PATCH 2/3] meta/classes/image: added isar_bootstrap_tarball task claudius.heine.ext
2018-05-23 6:32 ` [RFC PATCH 3/3] meta/isar-bootstrap: add 'do_restore_from_tarball' task claudius.heine.ext
2018-05-23 14:30 ` [RFC PATCH 0/3] Reproducible build Maxim Yu. Osipov
2018-05-23 15:20 ` Claudius Heine
2018-05-24 16:00 ` Henning Schild
2018-05-25 8:10 ` Claudius Heine
2018-05-25 11:57 ` Maxim Yu. Osipov
2018-05-25 17:04 ` Claudius Heine
2018-06-04 11:37 ` Baurzhan Ismagulov
2018-06-04 16:05 ` Claudius Heine
2018-06-05 10:42 ` Claudius Heine
2018-06-06 9:17 ` Claudius Heine
2018-06-06 14:20 ` Claudius Heine
2018-06-07 8:50 ` Baurzhan Ismagulov
2018-06-07 8:08 ` Maxim Yu. Osipov
2018-06-11 8:45 ` Claudius Heine
2018-06-11 13:51 ` Claudius Heine
2018-06-14 8:50 ` Claudius Heine
2018-06-20 4:20 ` Maxim Yu. Osipov
2018-06-20 8:12 ` Claudius Heine
2018-05-23 13:26 ` [RFC PATCH v2 " claudius.heine.ext
2018-05-23 13:26 ` [RFC PATCH v2 1/3] meta/isar-bootstrap-helper+dpkg.bbclass: bind mount /var/cache/apt/archives claudius.heine.ext
2018-05-23 13:26 ` [RFC PATCH v2 2/3] meta/classes/image: added isar_bootstrap_tarball task claudius.heine.ext
2018-05-23 13:26 ` [RFC PATCH v2 3/3] meta/isar-bootstrap: add 'do_restore_from_tarball' task claudius.heine.ext
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=20180523063206.29180-1-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.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