From: Tom Rini <trini@konsulko.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Introduce packagegroup-core-base-utils
Date: Fri, 1 Mar 2019 17:26:48 -0500 [thread overview]
Message-ID: <1551479212-28944-1-git-send-email-trini@konsulko.com> (raw)
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
next reply other threads:[~2019-03-01 22:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 22:26 Tom Rini [this message]
2019-03-01 22:26 ` [PATCH 1/4] vim: Import version 8.1.0347 Tom Rini
2019-03-02 9:15 ` Martin Jansa
2019-03-02 12:36 ` Tom Rini
2019-03-02 12:57 ` Tom Rini
2019-03-02 15:42 ` Joshua Watt
2019-03-01 22:26 ` [PATCH 2/4] inetutils: Import version 1.9.4 Tom Rini
2019-03-02 17:00 ` Richard Purdie
2019-03-02 17:46 ` Tom Rini
2019-03-02 19:25 ` Richard Purdie
2019-03-02 19:28 ` Tom Rini
2019-03-04 9:47 ` André Draszik
2019-03-04 16:40 ` Tom Rini
2019-03-01 22:26 ` [PATCH 3/4] packagegroup-core-base-utils: Introduce new base-utils packagegroup Tom Rini
2019-03-02 14:41 ` Tom Rini
2019-03-04 16:44 ` Mark Hatle
2019-03-04 18:02 ` Tom Rini
2019-03-01 22:26 ` [PATCH 4/4] imagefeatures: Add test to blacklist building busybox Tom Rini
2019-03-02 7:11 ` [PATCH 0/4] Introduce packagegroup-core-base-utils Adrian Bunk
2019-03-02 12:36 ` Tom Rini
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=1551479212-28944-1-git-send-email-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.