Hey all, Over on the Yocto list[1] the topic of how to build an image without busybox once again came up. As part of that discussion I said I'd been thinking about a packagegroup to make this easier to do as while virtual/base-utils and VIRTUAL-RUNTIME_base-utils exist and work and allow for this, the list of things we get from busybox is non-trivial. In fact, this exposed that in oe-core itself we have no editor aside from busybox and are missing a number of common network utilities too. To that end, this series migrates vim and inetutils from meta-oe to oe-core, introduces packagegroup-core-base-utils (and documents using it in local.conf.sample.extended) and finally adds a testcase of building (technically, making the dependency graph as that does what we need and is much quicker, 5s vs 3 minute) core-image-sato with busybox disabled, so that we can do our best to avoid introucing busybox as a hard requirement in the future.
With respect to functionality, this is basically 1:1 with busybox. I didn't add more "useful" utilities (which I would argue belong in packagegroup-core-full-cmdline which follow up to this could be enhanced to pull in this packagegroup and add to it). In terms of deviation: - We do not have a trivial dhcp server, unless you use systemd. - We may have also lost a few similar trivial servers. One may argue that by default maybe busybox shouldn't be opening this stuff up. - busybox provides "nslookup" which at this point in time is an anachronism. bind stopped shipping "nslookup" prior to oe-core replacing the old monolithic layer. We do provide host and dig and such via bind-utils. [1]: https://lists.yoctoproject.org/pipermail/yocto/2019-February/044317.html -- Tom -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core