From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [RFC][PATCH 0/6] Isar build reproducibility
Date: Wed, 3 Jan 2018 14:49:45 +0100 [thread overview]
Message-ID: <20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180102145744.21814-1-asmirnov@ilbers.de>
Am Tue, 2 Jan 2018 17:57:38 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> Hello all,
>
> this series proposes the way how build reproducibility could be
> implemented in Isar. General idea is to get the list of all the
> necessary packages for build, fetch them and create local repo, that
> will be used for further builds/
>
> Briefly speeking, it works like the following:
>
> 1. User sets the list of images that should be 'reproducible' in
> BASE_APT_IMAGES variable in local.conf file.
I am with Jan here, i would prefer an all or nothing approach.
> 2. Based on the list of images above, Isar will derive all the
> run-time and build dependencies for these images.
>
> 3. Using multistrap, Isar will fetch the list of packages and create
> base-apt local repository.
>
> 4. Now buildchroot and image root filesystems are generated using
> base-apt.
Patch5 makes base-apt and Isar the only repos for a rootfs/buildchroot.
How do images, not using BASE_APT, get packages that are not cached?
> Some notes:
>
> 1. base-apt repository is mounted to buildchroot, so Isar packages are
> able to install necessary deps via apt-get.
>
> 2. bitbake events are used to clean up buildchroot. I haven't found
> another way how base-apt could be unmounted. So it's mounted once
> before any package starts building and unmounted by bitbake event:
> bb.event.BuildCompleted.
>
> This series works good with latest next. Any comments are welcome.
>
> Happy New Year 2018! :-)
Same from me!
Henning
> With best regards,
> Alex
>
> Alexander Smirnov (6):
> base-apt: Introduce fetching upstream apt
> base-apt: Add to pipeline
> buildchroot: Switch to base-apt
> buildchroot: Add mount/umount for 'base-apt'
> image: Switch to base-apt
> base-apt: Add possibility to reuse
>
> meta-isar/conf/local.conf.sample | 8 ++
> .../recipes-core/images/files/multistrap.conf.in | 18 +---
> meta-isar/recipes-core/images/isar-image-base.bb | 5 +-
> meta/classes/dpkg-base.bbclass | 16 +++-
> meta/classes/image.bbclass | 13 ++-
> meta/classes/isar-events.bbclass | 21 +++++
> meta/conf/isar-bitbake.conf | 2 +
> meta/recipes-devtools/base-apt/base-apt.bb | 97
> ++++++++++++++++++++++ .../base-apt/files/distributions.in
> | 3 + .../base-apt/files/multistrap.conf.in | 28 +++++++
> meta/recipes-devtools/buildchroot/buildchroot.bb | 28 ++++++-
> .../buildchroot/files/configscript.sh | 1 -
> .../buildchroot/files/multistrap.conf.in | 18 +---
> 13 files changed, 217 insertions(+), 41 deletions(-)
> create mode 100644 meta/classes/isar-events.bbclass
> create mode 100644 meta/recipes-devtools/base-apt/base-apt.bb
> create mode 100644
> meta/recipes-devtools/base-apt/files/distributions.in create mode
> 100644 meta/recipes-devtools/base-apt/files/multistrap.conf.in
>
next prev parent reply other threads:[~2018-01-03 13:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 14:57 Alexander Smirnov
2018-01-02 14:57 ` [RFC][PATCH 1/6] base-apt: Introduce fetching upstream apt Alexander Smirnov
2018-01-02 16:15 ` Jan Kiszka
2018-01-02 17:02 ` Alexander Smirnov
2018-01-03 13:15 ` Henning Schild
2018-01-02 16:20 ` Jan Kiszka
2018-01-02 14:57 ` [RFC][PATCH 2/6] base-apt: Add to pipeline Alexander Smirnov
2018-01-03 13:32 ` Henning Schild
2018-01-03 17:24 ` Henning Schild
2018-01-02 14:57 ` [RFC][PATCH 3/6] buildchroot: Switch to base-apt Alexander Smirnov
2018-01-02 14:57 ` [RFC][PATCH 4/6] buildchroot: Add mount/umount for 'base-apt' Alexander Smirnov
2018-01-02 14:57 ` [RFC][PATCH 5/6] image: Switch to base-apt Alexander Smirnov
2018-01-02 14:57 ` [RFC][PATCH 6/6] base-apt: Add possibility to reuse Alexander Smirnov
2018-01-02 16:09 ` [RFC][PATCH 0/6] Isar build reproducibility Jan Kiszka
2018-01-02 16:58 ` Alexander Smirnov
2018-01-02 17:07 ` Jan Kiszka
2018-01-02 17:25 ` Jan Kiszka
2018-01-03 13:49 ` Henning Schild [this message]
2018-01-03 13:54 ` Jan Kiszka
2018-01-03 14:03 ` Henning Schild
2018-01-03 14:06 ` Jan Kiszka
2018-01-09 7:45 ` Alexander Smirnov
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=20180103144945.017b062a@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.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