From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH 2/3] build.sh: Install newly built packages
Date: Wed, 31 Jan 2018 22:55:06 +0300 [thread overview]
Message-ID: <b7279922-5a33-fb19-084f-010eea7038f4@ilbers.de> (raw)
In-Reply-To: <aa962821-e39f-d55e-bfac-2531af97d0ef@siemens.com>
On 01/31/2018 10:39 PM, Jan Kiszka wrote:
> On 2018-01-25 09:38, Alexander Smirnov wrote:
>> Install the debs to buildchroot immediately. This should go when Isar
>> apt will be integrated to buildchroot, so the next packages will be
>> able to populate build dependencies via 'apt-get install'.
>
> What makes adding the local repo to the buildchroot so complex? I would
> assume it's just
>
> - creating an empty repo already during buildchroot setup
The repo is already created outside the buildchroot.
> - adding the additional source to buildchroot's multistrap.conf
> - be happy
>
The isar-apt should be visible in buildchroot, so:
- We need to 'mount --bind' apt folder to buildchroot before packages
build started.
- Unmount this folder when all the packages are built.
- Cleanup the mount point if build fails.
I have working concept now, I'll send the series tomorrow.
Apart from changes above I've also fixed reprepro races protection and
isar-apt population.
Alex
next prev parent reply other threads:[~2018-01-31 19:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:38 [PATCH 0/3] Implement hello <-> libhello pattern Alexander Smirnov
2018-01-25 8:38 ` [PATCH 1/3] dpkg-base: Add dependecies between Isar recipes Alexander Smirnov
2018-02-05 19:40 ` Jan Kiszka
2018-02-06 10:10 ` chombourger
2018-02-06 20:25 ` Alexander Smirnov
2018-01-25 8:38 ` [PATCH 2/3] build.sh: Install newly built packages Alexander Smirnov
2018-01-31 19:39 ` Jan Kiszka
2018-01-31 19:55 ` Alexander Smirnov [this message]
2018-01-31 20:01 ` Jan Kiszka
2018-02-01 7:49 ` Benedikt Niedermayr
2018-02-01 8:07 ` Alexander Smirnov
2018-02-01 10:09 ` Benedikt Niedermayr
2018-02-01 11:37 ` Jan Kiszka
2018-01-25 8:38 ` [PATCH 3/3] libhello: Add libhello Alexander Smirnov
2018-01-25 9:01 ` Jan Kiszka
2018-01-25 10:11 ` Alexander Smirnov
2018-01-25 10:30 ` Jan Kiszka
2018-01-29 16:14 ` [PATCH 0/3] Implement hello <-> libhello pattern Henning Schild
2018-02-05 21:56 ` 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=b7279922-5a33-fb19-084f-010eea7038f4@ilbers.de \
--to=asmirnov@ilbers.de \
--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