From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>,
"[ext] Henning Schild" <henning.schild@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] use local repo for multistrap and drop "dpkg -i"
Date: Wed, 2 Aug 2017 09:04:36 +0200 [thread overview]
Message-ID: <f0819de5-1b97-b25f-e03f-3a80b13fe43c@siemens.com> (raw)
In-Reply-To: <1829ce20-c5b8-ec3c-f36b-fda83fc516ee@siemens.com>
On 08/02/2017 08:16 AM, [ext] Jan Kiszka wrote:
> On 2017-08-01 17:24, [ext] Henning Schild wrote:
>> This series introduces support for a local repository to be used instead
>> of "dpkg -i" after bootstrap. The do_populate task was dropped.
>>
>
> I think this also provides a nice path to extract all packages for
> archiving purposes and replay installations from them.
That would just archive your own packages though.
As we discussed offline, it would be nice to fetch all required packages
into an local repo first and then use just this repo to install
everything to the rootfs/buildchroot. This way you would not depend on
the package archiving from upstream. But I currently don't know how to
do that. Maybe we should look into what is possible with [1] and
integrate it into isar.
Cheers,
Claudius
[1] https://launchpad.net/python-apt/
>
> What would be a strategy to enable multiple Debian repo sources on top
> of that?
>
> Jan
>
>> It is based on the previous series i sent but it should not be too hard to
>> rebase it. Please let me know if it should be rebased.
>>
>> Henning Schild (3):
>> classes: images: remove cyclic "inherit"
>> classes: move rootfs into image class and split into tasks
>> classes: image: remove populate and replace it with a custom repo
>>
>> .../recipes-core/images/files/multistrap.conf.in | 10 ++-
>> meta-isar/recipes-core/images/isar-image-base.bb | 43 +-----------
>> meta/classes/ext4-img.bbclass | 4 +-
>> meta/classes/image.bbclass | 76 +++++++++++++++++-----
>> 4 files changed, 75 insertions(+), 58 deletions(-)
>>
>
next prev parent reply other threads:[~2017-08-02 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:24 Henning Schild
2017-08-01 15:24 ` [PATCH 1/3] classes: images: remove cyclic "inherit" Henning Schild
2017-08-01 15:24 ` [PATCH 2/3] classes: move rootfs into image class and split into tasks Henning Schild
2017-08-01 15:24 ` [PATCH 3/3] classes: image: remove populate and replace it with a custom repo Henning Schild
2017-08-09 6:21 ` Henning Schild
2017-08-02 6:16 ` [PATCH 0/3] use local repo for multistrap and drop "dpkg -i" Jan Kiszka
2017-08-02 7:04 ` Claudius Heine [this message]
2017-08-02 8:15 ` Henning Schild
2017-08-02 8:11 ` Henning Schild
2017-08-02 8:12 ` Henning Schild
2017-08-03 19:17 ` Henning Schild
2017-08-10 12:46 ` Baurzhan Ismagulov
2017-08-11 8:13 ` Henning Schild
2017-08-11 15:36 ` Baurzhan Ismagulov
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=f0819de5-1b97-b25f-e03f-3a80b13fe43c@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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