From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"Quentin Schulz" <quentin.schulz@cherry.de>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v2] dev-manual: mention that "bmap-tools" is transitional package
Date: Mon, 22 Jun 2026 10:03:48 +0200 [thread overview]
Message-ID: <DJFF71VOMOX3.QQ7JIW3WTEM@bootlin.com> (raw)
In-Reply-To: <35ff1c1f-1331-8675-be8a-ddec3baf0283@crashcourse.ca>
On Fri Jun 19, 2026 at 8:32 PM CEST, Robert P. J. Day wrote:
> On Fri, 19 Jun 2026, Quentin Schulz wrote:
[...]
>> > + - Finally, in modern Ubuntu and Debian releases, the ``bmap-tools``
>> > + package is a transitional package; it exists solely to ensure
>> > + backward compatibility and smooth upgrades from older installations.
>> > + You can safely remove it and install the active package,
>> > ``bmaptool``,
>> > + which contains the actual utilities for flashing block images.
>> > +
>>
>> Just list this in the first bullet point which is related to Ubuntu and Debian
>> distributions?
>>
>> I could see switching the default package to install from bmap-tools to
>> bmaptool and add a note (Sphinx note) that on older releases, it was named
>> bmap-tools so install that package instead.
>>
>> Note that Fedora 43+ has bmap-tools, and Leap 16+
>> python3-bmap-tools/python3-bmaptools.
>
> my patch was already merged into master-next, but i like your
> suggestion so if antonin thinks it's worth it, he can revert that
> earlier patch and i can do it your way.
I dropped it, I also like Quentin's suggestion.
Thanks both,
Antonin
prev parent reply other threads:[~2026-06-22 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:34 [PATCH v2] dev-manual: mention that "bmap-tools" is transitional package Robert P. J. Day
2026-06-19 15:18 ` [docs] " Quentin Schulz
2026-06-19 18:32 ` Robert P. J. Day
2026-06-22 8:03 ` Antonin Godard [this message]
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=DJFF71VOMOX3.QQ7JIW3WTEM@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=rpjday@crashcourse.ca \
/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