On Mon, 20 Mar 2023 at 07:15, Mikko Rapeli <[email protected]> wrote: > > But then we should put e2fsprogs into buildtools-tarball(-extended). It’s > > not any different to providing compatible gcc, when one from the host > > distro is too old. > > I think this one is a bit different. At flashing/install step people > frequently manipulate rootfs images coming out of yocto builds to match > what HW and various boards actually have, like extending the file system > to fill full EMMC/SD cards. Like dd the .wic out of a build but extend > the file system for the full disk before first boot on the system.
Sorry Mikko, I'm putting my foot down on this. Yocto does not promise that random tools 'from the host' are going to work for its artefacts, and should not start making that promise. We are not Debian, and we do not promise compatibility with Debian or anyone else beyond what is allowed in HOSTTOOLS. You can instruct developers in your organization to install the tarball and use tools from it for those manipulations. You can also just carry the needed custom patches for e2fsprogs in your builds. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#178800): https://lists.openembedded.org/g/openembedded-core/message/178800 Mute This Topic: https://lists.openembedded.org/mt/97669707/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
