From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] rootfs: Use separate mounts lock file
Date: Fri, 9 Jul 2021 15:43:01 +0300 [thread overview]
Message-ID: <68459ec1-9588-5ac5-e414-c1f5dcb147b1@ilbers.de> (raw)
In-Reply-To: <f56b5d45-7bdf-2548-5544-abf691985add@siemens.com>
08.07.2021 20:37, Jan Kiszka wrote:
> Definitely a good catch, but I'm still wrapping my head around it. We
> either have really separated rootfs'es here so that separated lock files
> are fine, or we rather want rootfs_do_mounts to be locked against
> buildchroot_do_mounts as well. At least conceptually, even if they well
> never run in parallel in practice. In that case, MOUNT_LOCKFILE in
> rootfs.bbclass should be made a weak assignment, to clarify that
> buildchroot.bbclass will win, irrespective of any ordering.
It mostly depends on what MOUNT_LOCKFILE was originally introduced for.
Looks like it's all starts from 48ed716 Move buildchroot mounts into
dpkg-base class.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-07-09 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 15:22 Anton Mikanovich
2021-07-08 17:37 ` Jan Kiszka
2021-07-09 12:43 ` Anton Mikanovich [this message]
2021-07-26 14:44 ` Anton Mikanovich
2021-07-26 15:46 ` Baurzhan Ismagulov
2021-07-26 16:01 ` Jan Kiszka
2021-08-18 10:26 ` Anton Mikanovich
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=68459ec1-9588-5ac5-e414-c1f5dcb147b1@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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