Re: [RFC PATCH] Remove isar-apt and the corresponding lock

[Raphael Lisicki <raphael.lisicki@siemens.com>]

On 19.10.22 12:47, Adriaan Schmidt wrote:
> Hi all,
> 
> the isar-apt file lock has been bothering me for a while now, mainly because
> it leads to situations where we see many bitbake tasks running in parallel,
> but unable to make any progress (deploy_deb, install_builddeps, ...).
> 
> I ran a quick experiment on what would be required to change that, and
> came up with this approach:
> - isar-apt/ is no longer a repository maintained with reprepro
> - each recipe has "its own" directory below isar-apt/
> - there are directories isar-apt/${PN}/in and isar-apt/${PN}/out
> - out/ contains the deb packages produced, put there by deploy_deb
> - in/ is populated by prepare_build and contains the contents of in/ and out/
>    of all DEPENDS (need all the in/ contents due to transitive dependencies)
> - then, again in prepare_build, we copy our in/ directory to WORKDIR, and
>    create an apt repository (actually just a "Packages" file) using dpkg-scanpackages.
> 
> In addition to removing the lock, this also gives us better control
> over what goes into a package build, and eliminates effects due to "accidental"
> packages in isar-apt.

This sounds like a great side-effect. Love it.


> 
> I've implemented a very rough PoC, just to give you an idea. Please don't
> look too closely at the code, there are many things missing (e.g. SDKs,
> architectures != amd64, ...). But it can build isar-image-base for amd64.
> 
> If we decide that this would be a worthwile change, I will spend some
> more time on it.
> 
> Best,
> Adriaan

best regards
raphael