Re: [PATCH 0/5] support creation of a full repo for offline/reproducible builds

[Benedikt Niedermayr <benbrenson89@googlemail.com>]

Am 05.02.2018 um 11:26 schrieb Alexander Smirnov:
> In other words, there should be the only one component/recipe who 
> fetches the upstream packages.
>
> There is still open question, how to fetch all the packages: in a 
> single step or during the build.
>
> I want to have an option similar to Yocto's one: -c fetchall to have 
> possibility to fetch all the necessary artifacts and do not depend 
> from network anymore. 

Meanwhile I'm with you, in terms of your proposal. Fetching all packages 
at the beginning, would be easier to achive.
Otherwise I have no Idea how to solve potential remote repository 
updates between buildchroot and rootfs steps.


The other problem would be to resolve dependencies at the beginning of 
the build process.
I think "aptly" can do that hard work for us.
But this would require to replace reprepro with aptly.

I will implement a PoC with aptly which should cover the following:

1. Extract DEBIAN_DEPENDS from all recipes, as well as IMAGE_PREINSTALL 
and BUILDCHROOT_PREINSTALL.

2. Create an aptly mirror by setting the "-filter" option.
Aptly will resolve all dependencies when setting the filter option.
This is the most important step. If aptly fails to resolve dependencies 
correctly, I will abort my PoC.

3. Create a local Repo for Isar packages.

4. Start the build and let do_rootfs() refer to local mirror.


Benni