On 14 Nov 2023, at 21:04, Dmitry Baryshkov via lists.openembedded.org 
<[email protected]> wrote:
> 
> The Android's simg2img/img2simg comes from android-tools, which is a
> huge package with lots of dependencies on its own. It resides inside
> meta-oe rather than OE-Core. Add lightweight tool to handle sparse
> images, which is small enough to be pushed into OE-Core.

Amusingly I saw this before the other post.

Why should this be in core?  We already have bmap for the use-case of “sparse 
images”.  What’s the rationale for adding two tools that do the same thing?

Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#190809): 
https://lists.openembedded.org/g/openembedded-core/message/190809
Mute This Topic: https://lists.openembedded.org/mt/102592508/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to