From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Claudius Heine <ch@denx.de>,
Henning Schild <henning.schild@siemens.com>,
"[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [RFC PATCH 0/3] Reproducible build
Date: Fri, 25 May 2018 13:57:18 +0200 [thread overview]
Message-ID: <a3f5bf99-6023-c254-b781-1ce89ffac0b1@ilbers.de> (raw)
In-Reply-To: <d25dbbeb-0c03-75cf-8ebb-cb5f41004c7e@denx.de>
Hi Claudius,
Let me summarize the patchset status.
1. This patchset is just a first step towards more generic traceable
reproducible build - tarball versioning/reproducibility features are out
of scope of this patch set.
2. Baurzhan always asks to provide some bits of information into the
documentation when a new feature is added (or changed).
3. Henning asked about "stealing DL_DIR of bitbake as well" (see his
email below). What is your opinion?
Kind regards,
Maxim.
On 05/25/2018 10:10 AM, Claudius Heine wrote:
> Hi Henning,
>
> On 05/24/2018 06:00 PM, Henning Schild wrote:
>> Am Wed, 23 May 2018 08:32:03 +0200
>> schrieb "[ext] claudius.heine.ext@siemens.com"
>> <claudius.heine.ext@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.
>>
>> I did not look at the patches yet. And because it sounds so simple my
>> first reaction is that it can not be complete.> One thing we will need for sure is the sources that lead to the
>> packages we built ourselfs, otherwise we can not rebuild them later on.
>> And that seems to be a tricky part, not covered by stealing the cache.
>
> You are right, this solution is not complete and Rom was not build on
> one day. My goal was to improve the situation just one small step and
> then build on top of it.
>
>> Maybe stealing the DLDIR of bitbake as well?
>>
>>> 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.
>>
>> Are you sure that "apt-get clean" is the only reason for cache
>> eviction? What will happen if i install a ton of packages, not that apt
>> will want to safe space at some point.
>
> Yes, I might be useful to set the apt.conf to disable all autocleaning
> options.
> But normally apt removes packages from cache only if they are no longer
> downloadable and since the local index of the upstream repos are not
> updated it shouldn't detect if they are no longer downloadable and
> therefore not remove them. Disabling this completely is still the better
> option.
>
> Claudius
>
>>
>> Henning
>>
>>> 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(-)
>>>
>>
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-05-25 11:57 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 ` [RFC PATCH 0/3] Reproducible build claudius.heine.ext
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 [this message]
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=a3f5bf99-6023-c254-b781-1ce89ffac0b1@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@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