From: cedric_hombourger@mentor.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] dpkg: acquire a read (shared) locks while building packages
Date: Fri, 8 Mar 2019 07:24:30 -0800 (PST) [thread overview]
Message-ID: <6cd427c7-087d-44e5-9dcc-082b97eeb0bb@googlegroups.com> (raw)
In-Reply-To: <a90bcb21-d11c-368e-173a-4004375e8860@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 823 bytes --]
>
> 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 :)
Cedric
[-- Attachment #1.2: Type: text/html, Size: 1121 bytes --]
next prev parent reply other threads:[~2019-03-08 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 9:57 Cedric Hombourger
2019-03-08 10:04 ` Jan Kiszka
2019-03-08 13:33 ` cedric_hombourger
2019-03-08 15:13 ` Jan Kiszka
2019-03-08 15:24 ` cedric_hombourger [this message]
2019-03-08 15:27 ` Jan Kiszka
2019-03-08 15:49 ` [PATCH v2] " Cedric Hombourger
2019-03-08 16:38 ` Jan Kiszka
2019-03-14 6:21 ` cedric_hombourger
2019-03-15 4:47 ` Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6cd427c7-087d-44e5-9dcc-082b97eeb0bb@googlegroups.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox