Re: [PATCH] dpkg: acquire a read (shared) locks while building packages

[Jan Kiszka <jan.kiszka@siemens.com>]

On 08.03.19 16:24, cedric_hombourger@mentor.com wrote:
>     Then let's also patch meta/recipes-kernel/linux/linux-custom.inc analogously
>     and
>     leave external dpkg_runbuild to downstream.
> 
> 
> it should be noted that "make dpkg-deb" does not use debhelper (as I recently 
> found while modifying the kernel builddep script to also package perf and
> wondering why my shlibs variables were not parsed)
> 
> So, to the best of my knowledge, the current (mainline) package scripts from the 
> kernel will not access the dpkg database. so are we wanting to be
> extra safe and grab a shared lock anyway (which will block other bitbake threads 
> from running do_install_deps or do_deploy_deb while the kernel
> builds since bitbake grabs an exclusive lock for these tasks) OR use this 
> "knowledge" to keep some parallelism.
> 
> I am fine either way - just wanted to expose both options :)

Indeed, then we are safe at this point. If you sent v2, please add this reason 
to the changelog. Hopefully, the person will read that who adds kernel tool 
packaging via debhelpers one day. ;)

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux