public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Reproducibility of builds
Date: Thu, 3 Aug 2017 10:13:12 +0200	[thread overview]
Message-ID: <ec5a4a95-1135-1a1f-90b4-55e7106b8491@siemens.com> (raw)

Hi,

am I right that Isar supports or should support reproducible root file 
system build?

If I understand correctly, when multistrap is called, it fetches always 
the latest version of all packages from the debian repository mirrors. 
Am I mistaken or is this feature still on the roadmap?

I that is on the roadmap, how are you thinking of solving this issue?

The openembedded way would be to seperate the fetch and 'install' step 
and first download all packages into the DL_DIR and then use them from 
there. Maybe we could create this pipeline:

dpkg-binary Recipe:

fetch deb file into downloads -> insert into local repository

dpkg-source Recipe:

fetch sources into downloads -> build packages -> insert into local 
repository

image Recipe:

fetch all required packages into downloads -> insert all of them into 
the local repository -> create root fs using only the local repository

Multistrap provides a '--source-dir DIR' parameter, that stores all 
installed packages into a directory. So if we would use that as a 
fetcher, then we would create a temporary rootfs just to get all 
required packages for the project.

Are there other possible solutions for this?

Cheers,
Claudius


             reply	other threads:[~2017-08-03  8:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  8:13 Claudius Heine [this message]
2017-08-21 11:23 ` Claudius Heine
2017-08-28 11:27   ` Claudius Heine
2017-09-05 10:05     ` Alexander Smirnov
2017-09-05 10:38       ` Jan Kiszka
2017-09-05 11:50         ` Alexander Smirnov
2017-09-05 11:54       ` Claudius Heine
2017-09-06 13:39         ` Claudius Heine
2017-09-18 15:05 ` Baurzhan Ismagulov
2017-09-19  8:55   ` Claudius Heine
2017-11-14 16:04 ` Christian Storm
2017-11-14 16:22   ` Claudius Heine
2017-11-17 16:53     ` [ext] Christian Storm
2017-11-17 18:14       ` Claudius Heine
2017-11-20  8:33         ` [ext] Christian Storm
2017-11-20  9:16           ` Claudius Heine
2017-11-29 18:53             ` Alexander Smirnov
2017-11-29 19:02               ` Jan Kiszka
2017-11-30  8:04                 ` Alexander Smirnov
2017-11-30 14:48                   ` Jan Kiszka
2017-11-30  9:31               ` Claudius Heine
2017-12-06 16:21                 ` 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=ec5a4a95-1135-1a1f-90b4-55e7106b8491@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --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