From: Jan Kiszka <jan.kiszka@siemens.com>
To: Benedikt Niedermayr <benbrenson89@googlemail.com>,
isar-users@googlegroups.com
Cc: Benedikt Niedermayr <Benedikt.Niedermayr@mixed-mode.de>
Subject: Re: [PATCH 0/6] Local apt cache with aptly
Date: Tue, 6 Feb 2018 14:00:35 +0100 [thread overview]
Message-ID: <c5246314-de9c-1317-dc3d-a55001971ae0@siemens.com> (raw)
In-Reply-To: <1517911779-30507-1-git-send-email-Benedikt.Niedermayr@mixed-mode.de>
On 2018-02-06 11:09, 'Benedikt Niedermayr' via isar-users wrote:
> Hi all,
> this series implements a PoC for running reproducible builds.
> The core is based on aptly, which is a nice mirroring tool for debian repositories.
>
> The mirroring solution does the following:
> - Aptly generates a mirrors for upstream repositories as well as snapshots and also a local repository for isar packages.
> - Get a list of all packages for mirroring before rootfs and buildchroot is beeing created.
> This is done by running an own bitbake cooker for parsing the recipes by taking append files,
> configs, datastore and also selected layers(bblayers) into account.
> This solves the problem when upstream repos getting updates between rootfs and buildchroot creation.
> - Aptly will recieve the list of packages and calculates all further required dependencies for the mirror.
> - Rootfs and buildchroot will never pull from upstream repos but instead from the local mirrors.
>
>
> Open Questions:
> - Think about a more dynamic multistrap.conf generation. Ŕunning sed to multiconfig templates is not really flexible.
> - Get a better naming convention for aptly mirrors, snapshots and repos. This will help to get multiconfig compatible.
> Where are pros and cons here?
> - Where to store the cache? TMPDIR might not be the best location.
>
> This series is based on commit 384750d of next branch.
> Running with multiconfig was not tested, yet. But maybe you can do it?
>
>
> Benedikt Niedermayr (6):
> Implement support for setting up the local apt mirror and isar
> repository with aptly.
> Added API class for apt cache.
Ordering of patch 1 and 2 is wrong.
Jan
> Added apt-cache functionality for buildchroot.
> Added apt-cache functionality for image rootfs.
> Added do_finalize_image task.
> Added support for installing isar packages to local isar repository.
>
> .../recipes-core/images/files/multistrap.conf.in | 8 +-
> meta-isar/recipes-core/images/isar-image-base.bb | 22 +-
> meta/classes/apt-cache.bbclass | 235 +++++++++++++++++++++
> meta/classes/dpkg-base.bbclass | 15 +-
> meta/classes/image.bbclass | 23 +-
> meta/recipes-devtools/buildchroot/buildchroot.bb | 35 ++-
> .../buildchroot/files/multistrap.conf.in | 17 +-
> meta/recipes-devtools/isar-apt/files/aptly.conf.in | 17 ++
> meta/recipes-devtools/isar-apt/isar-apt.bb | 131 ++++++++++--
> 9 files changed, 454 insertions(+), 49 deletions(-)
> create mode 100644 meta/classes/apt-cache.bbclass
> create mode 100644 meta/recipes-devtools/isar-apt/files/aptly.conf.in
>
> --
> 2.7.4
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-02-06 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 10:09 Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 1/6] Implement support for setting up the local apt mirror and isar repository " Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 2/6] Added API class for apt cache Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 3/6] Added apt-cache functionality for buildchroot Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 4/6] Added apt-cache functionality for image rootfs Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 5/6] Added do_finalize_image task Benedikt Niedermayr
2018-02-06 10:09 ` [PATCH 6/6] Added support for installing isar packages to local isar repository Benedikt Niedermayr
2018-02-06 12:39 ` [PATCH 0/6] Local apt cache with aptly Jan Kiszka
2018-02-06 13:28 ` Jan Kiszka
2018-02-06 14:03 ` Benedikt Niedermayr
2018-02-06 14:26 ` Hombourger, Cedric
2018-02-06 13:00 ` Jan Kiszka [this message]
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=c5246314-de9c-1317-dc3d-a55001971ae0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Benedikt.Niedermayr@mixed-mode.de \
--cc=benbrenson89@googlemail.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