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 :)

Cedric