From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: [PATCH] dev-manual: update bmaptool section, refer to "bmaptool" package
Date: Tue, 16 Jun 2026 12:22:16 -0400 (EDT) [thread overview]
Message-ID: <b3901bb2-dbcc-3145-caec-c2dfb87f5dc9@crashcourse.ca> (raw)
Update the section on "bmaptool" to use the newer "bmaptool" package
name rather than the older "bmap-tools" name (which still exists but
is simply a transitional package).
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/documentation/dev-manual/bmaptool.rst b/documentation/dev-manual/bmaptool.rst
index 87162a49c..29e7f0d2e 100644
--- a/documentation/dev-manual/bmaptool.rst
+++ b/documentation/dev-manual/bmaptool.rst
@@ -13,13 +13,13 @@ system image files much faster.
.. note::
- If you are using Ubuntu or Debian distributions, you can install
- the ``bmap-tools`` package using the following command and then
+ the ``bmaptool`` package using the following command and then
use the tool without specifying ``PATH`` even from the root
account::
- $ sudo apt install bmap-tools
+ $ sudo apt install bmaptool
- - If you are unable to install the ``bmap-tools`` package, you will
+ - If you are unable to install the ``bmaptool`` package, you will
need to build `bmaptool` before using it. Use the following command::
$ bitbake bmaptool-native -caddto_recipe_sysroot
@@ -56,3 +56,10 @@ For help on the ``bmaptool`` command, use the following command::
$ bmaptool --help
+.. note::
+
+ Earlier releases of Ubuntu and Debian had a package named
+ ``bmap-tools``; you can still install by this name as this
+ is simply a transitional package which exists solely to
+ ensure backward compatibility and smooth upgrades from
+ older installations.
reply other threads:[~2026-06-16 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b3901bb2-dbcc-3145-caec-c2dfb87f5dc9@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=docs@lists.yoctoproject.org \
/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