public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH 1/3] mount: Add unmount requirement to API changelog
Date: Wed, 30 Jun 2021 14:35:45 +0300	[thread overview]
Message-ID: <20210630113547.87295-2-amikan@ilbers.de> (raw)
In-Reply-To: <20210630113547.87295-1-amikan@ilbers.de>

After the latest mount rebuild any usage of mount functions should be
ended with the following unmount call.

Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
 RECIPE-API-CHANGELOG.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 806c291..546d91c 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -292,3 +292,24 @@ Migrate your patches so they can be applied with "git am", or
 
 Kernel image name for arm64 platforms is vmlinux now. Image format was
 not changed (uncompressed executable) but now it is named correctly.
+
+### Make unmounting mandatory
+
+There were mount API to provide some path inside chroots:
+```
+dpkg_do_mounts
+buildchroot_do_mounts
+image_do_mounts
+rootfs_do_mounts
+```
+
+From now those calls should be always followed by unmount actions:
+
+```
+dpkg_undo_mounts
+buildchroot_undo_mounts
+image_undo_mounts
+rootfs_undo_mounts
+```
+
+It case any unmounted paths left at the end of build warnings will be thrown.
-- 
2.25.1


  reply	other threads:[~2021-06-30 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 11:35 [PATCH 0/3] Update Isar documentation Anton Mikanovich
2021-06-30 11:35 ` Anton Mikanovich [this message]
2021-06-30 12:11   ` [PATCH 1/3] mount: Add unmount requirement to API changelog Jan Kiszka
2021-06-30 11:35 ` [PATCH 2/3] doc: Update tasks description Anton Mikanovich
2021-06-30 11:35 ` [PATCH 3/3] doc: Update available image types 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=20210630113547.87295-2-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --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