From: <kazuhiro3.hayashi@toshiba.co.jp>
To: <henning.schild@siemens.com>
Cc: <claudius.heine.ext@siemens.com>, <isar-users@googlegroups.com>,
<meta-eid@googlegroups.com>
Subject: Re: multistrap support
Date: Wed, 27 Feb 2019 09:08:43 +0000 [thread overview]
Message-ID: <TYXPR01MB182270CC671628C53C038ADAE1740@TYXPR01MB1822.jpnprd01.prod.outlook.com> (raw)
Hi Henning,
> > (snipped)
> > I usually create Debian based rootfs using only Debian official
> > packages (without other custom repos) and need to make it reproducible
> > in product development.
> > The way to do that is just keeping all package + version list in one
> > file.
> >
> > 1st build:
> > 1. Download required packages from Debian mirror
> > 2. Create a local repository with the packages downloaded in 1
> > 3. Generate package + version list registered in the local
> > repo 4. debootstrap with the local repo
> > 5. chroot apt install with the local repo
> > Rebuild:
> > 1. Download required packages listed in the list from Debian
> > mirror (created in 3 in the 1st build)
> > 2. Same as 2, 4, 5 in the 1st build.
> >
> > This might work when we use multiple apt repos.
> > Disadvantages are the time to build the local repository and
> > the time to create the package list.
> > Also we need to keep the package list for each build somewhere.
>
> Isar has support for something like that. Check out
> ISAR_USE_CACHED_BASE_REPO
>
> https://github.com/ilbers/isar/blob/next/doc/user_manual.md#creation-o
> f-local-apt-repo-caching-upstream-debian-packages
>
> That is not the final solution and has several open points.
>
> Henning
Thank you for the information.
I talked with Maxim yesterday about this topic and understand
how to generate "downloads/base-apt".
Kind regards,
Kazu
next reply other threads:[~2019-02-27 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 9:08 kazuhiro3.hayashi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-25 17:08 kazuhiro3.hayashi
2019-02-25 17:59 ` Henning Schild
2019-02-18 3:04 kazuhiro3.hayashi
2019-02-13 13:14 kazuhiro3.hayashi
2019-02-13 13:56 ` Claudius Heine
2019-02-13 15:18 ` Henning Schild
2019-02-14 6:08 ` kazuhiro3.hayashi
2019-02-13 16:15 ` Jan Kiszka
2019-02-14 10:14 ` kazuhiro3.hayashi
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=TYXPR01MB182270CC671628C53C038ADAE1740@TYXPR01MB1822.jpnprd01.prod.outlook.com \
--to=kazuhiro3.hayashi@toshiba.co.jp \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=meta-eid@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