Re: [PATCH 2/3] build.sh: Install newly built packages

[Alexander Smirnov <asmirnov@ilbers.de>]

On 02/01/2018 10:49 AM, Benedikt Niedermayr wrote:
> Am 31.01.2018 um 21:01 schrieb Jan Kiszka:
>> On 2018-01-31 20:55, Alexander Smirnov wrote:
>>> 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.
>> Great, looking forward!
>>
>> I've just switched my Jailhouse demo-image build over to the custom
>> kernel recipe helper I'm preparing, and proper Build-Depends support
>> would make the recipes even nicer.
>>
>> Jan
>>
> Am I right, that building own packages from own repositories is not 
> supported yet by Isar?

Doch! :-)

> 
> When I take a look into dpkg-raw class, I can see that dpkg_runbuild() 
> only creates a debian package, but does not build the package out from 
> it sources?

Please take a look to dpkg class and to example-hello application.

Alex