From: Benedikt Niedermayr <benbrenson89@googlemail.com>
To: Cedric_Hombourger@mentor.com, isar-users@googlegroups.com
Subject: Re: [PATCH 0/5] support creation of a full repo for offline/reproducible builds
Date: Mon, 5 Feb 2018 11:08:39 +0100 [thread overview]
Message-ID: <6ca3bedb-e829-0e07-c29b-cc19df848d7f@googlemail.com> (raw)
In-Reply-To: <20180204175454.220-1-Cedric_Hombourger@mentor.com>
Am 04.02.2018 um 18:54 schrieb Cedric_Hombourger@mentor.com:
> From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
>
> The package repository created by isar using reprepro only includes packages by isar.
> To support offline/reproducible builds, this changeset adds a do_populate task to
> augment the repo with packages used during the build. The task may be used against
> the buildchroot and images recipes. It should be noted that isar currently assumes
> that the base distribution will provide both an -updates and security feed. This is
> certainly true for Debian but may not be the case for other distributions or when
> when using our own feed.
>
> Some rework may be needed if the isar-apt changes get merged first. Conceptually the
> implementation may not change much (as far as I can tell!)
>
> Please review and let me know if any rework is required.
>
> Cedric Hombourger (5):
> base: add populate_repo task to include distro packages to the repo
> meta: move reprepro handling code to its own class
> buildchroot: use reprepro to populate the full repo
> reprepro: create the -updates distribution
> multistrap: make the security feed optional
>
> .../recipes-core/images/files/distributions.in | 4 +
> .../recipes-core/images/files/multistrap.conf.in | 14 ++--
> meta-isar/recipes-core/images/isar-image-base.bb | 86 ++++++++++++++++++++++
> meta/classes/image.bbclass | 47 +-----------
> meta/classes/reprepro.bbclass | 52 +++++++++++++
> meta/recipes-devtools/buildchroot/buildchroot.bb | 20 +++++
> .../buildchroot/files/distributions.in | 7 ++
> .../buildchroot/files/multistrap.conf.in | 10 +--
> 8 files changed, 182 insertions(+), 58 deletions(-)
> create mode 100644 meta/classes/reprepro.bbclass
> create mode 100644 meta/recipes-devtools/buildchroot/files/distributions.in
>
Hi Cedric,
thanks.
Pulling packages from the local repository for subsequent builds is not
implemented here?
Benni
next prev parent reply other threads:[~2018-02-05 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 17:54 Cedric_Hombourger
2018-02-04 17:54 ` [PATCH 1/5] base: add populate_repo task to include distro packages to the repo Cedric_Hombourger
2018-02-05 10:06 ` Alexander Smirnov
2018-02-04 17:54 ` [PATCH 2/5] meta: move reprepro handling code to its own class Cedric_Hombourger
2018-02-04 17:54 ` [PATCH 3/5] buildchroot: use reprepro to populate the full repo Cedric_Hombourger
2018-02-04 17:54 ` [PATCH 4/5] reprepro: create the -updates distribution Cedric_Hombourger
2018-02-04 17:56 ` [PATCH 5/5] multistrap: make the security feed optional Cedric_Hombourger
2018-02-05 7:18 ` [PATCH 0/5] support creation of a full repo for offline/reproducible builds Jan Kiszka
2018-02-05 9:11 ` Benedikt Niedermayr
2018-02-05 10:26 ` Alexander Smirnov
2018-02-05 10:31 ` Jan Kiszka
2018-02-05 11:22 ` Benedikt Niedermayr
2018-02-05 10:08 ` Benedikt Niedermayr [this message]
2018-02-05 10:16 ` chombourger
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=6ca3bedb-e829-0e07-c29b-cc19df848d7f@googlemail.com \
--to=benbrenson89@googlemail.com \
--cc=Cedric_Hombourger@mentor.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