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>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>,
Alexander Smirnov <asmirnov@ilbers.de>
Subject: Re: [PATCH 0/6] Local apt cache with aptly
Date: Tue, 6 Feb 2018 14:28:57 +0100 [thread overview]
Message-ID: <4ec03380-fb4f-ae64-0cde-4172235f4e7b@siemens.com> (raw)
In-Reply-To: <3c6785b1-1b80-e406-e499-515f89b055b9@siemens.com>
On 2018-02-06 13:39, [ext] Jan Kiszka wrote:
> On 2018-02-06 11:09, 'Benedikt Niedermayr' via isar-users wrote:
>> 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.
>
> This will not address the case of generated debian/control files and
> their Build-Depends, right? I'm not a fan of trying to extract the
> information in such a collection run, simply because of such tricky
> restrictions. Therefore, my proposal is to postpone any up-front
> fetching to later, if at all.
Hmm, does your patch address Build-Depends at all? Can you explain how
they make it into the aptly mirror filter?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-06 13:28 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 [this message]
2018-02-06 14:03 ` Benedikt Niedermayr
2018-02-06 14:26 ` Hombourger, Cedric
2018-02-06 13:00 ` Jan Kiszka
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=4ec03380-fb4f-ae64-0cde-4172235f4e7b@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Benedikt.Niedermayr@mixed-mode.de \
--cc=Cedric_Hombourger@mentor.com \
--cc=asmirnov@ilbers.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