From: Adrian Bunk <bunk@stusta.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Tom Rini <trini@konsulko.com>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Removing busybox
Date: Thu, 28 Feb 2019 07:19:45 +0200 [thread overview]
Message-ID: <20190228051945.GB11051@localhost> (raw)
In-Reply-To: <CAJTo0LbvYvSrcOegU+iCj6Q2yHwyNefm4gW8k8MzGQntJQGNqw@mail.gmail.com>
On Wed, Feb 27, 2019 at 11:59:42PM +0000, Burton, Ross wrote:
> On Wed, 27 Feb 2019 at 23:55, Tom Rini <trini@konsulko.com> wrote:
> > My current incomplete list is:
> > bind-utils \
> > bridge-utils \
> > coreutils \
> > dnsmasq \
> > e2fsprogs \
> > e2fsprogs-resize2fs \
> > e2fsprogs-tune2fs \
> > findutils \
> > gawk \
> > grep \
> > inetutils-ping \
> > inetutils-ping6 \
> > inetutils-traceroute \
> > iproute2 \
> > less \
> > net-tools \
> > parted \
> > pciutils \
> > procps \
> > sed \
> > util-linux \
> > vim \
> > which \
> >
> > And it's also incomplete as there's more stuff under inetutils I don't
> > need (but others may), and I set aside patch/diff/ed and some other
> > stuff I don't need. And since some of that stuff comes from
> > meta-openembedded, it's indeed really not clear how/where a packagegroup
> > would reside as we need things out of meta-networking.
>
> That's a good start. For a oe-core packagegroup
I do not think a core-only packagegroup makes sense when the goal is to
completely replace busybox (and not just most apps while keeping a few
busybox apps installed).
> I'd suggest dropping
> dnsmasq bridgeutils bindutils to keep it lean.
The stated usecases are not "lean" but "replace all busybox commands
with the full versions".
For that you need bind-utils (in oe-core) for DNS lookup.
>...
> Also swap vim for something in core obviously.
It is not obvious how to do that.
What other vi implementation is in core?
Is there even any good non-busybox non-GUI editor in core?
Replacing busybox vi with ed would be a bad fit for the
stated usecases.
There has to be some vi implementation installed,
and the "desktop command" implementation is vim.
> Ross
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-02-28 5:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 12:16 Removing busybox Jean-Christian de Rivaz
2019-02-27 17:06 ` Tom Rini
2019-02-27 17:25 ` Mark Hatle
2019-02-27 17:42 ` Burton, Ross
2019-02-27 17:58 ` Tom Rini
2019-02-27 18:35 ` Burton, Ross
2019-02-27 18:45 ` Tom Rini
2019-02-27 18:47 ` Burton, Ross
2019-02-27 18:54 ` Tom Rini
2019-02-27 18:48 ` Scott Rifenbark
2019-02-28 18:43 ` Tom Rini
2019-02-27 20:06 ` Jean-Christian de Rivaz
2019-02-27 20:09 ` Tom Rini
2019-02-27 21:31 ` Paul Eggleton
2019-02-27 21:35 ` Tom Rini
2019-02-27 21:40 ` Adrian Bunk
2019-02-27 21:46 ` Tom Rini
2019-02-27 21:49 ` Burton, Ross
2019-02-27 22:24 ` Jean-Christian de Rivaz
2019-02-27 22:58 ` Philip Balister
2019-02-27 23:02 ` Burton, Ross
2019-02-27 23:54 ` Tom Rini
2019-02-27 23:59 ` Burton, Ross
2019-02-28 0:10 ` Jean-Christian de Rivaz
2019-02-28 0:11 ` Burton, Ross
2019-02-28 5:19 ` Adrian Bunk [this message]
2019-02-28 12:05 ` Burton, Ross
2019-02-28 14:27 ` Richard Purdie
2019-02-28 14:37 ` Tom Rini
2019-02-28 14:55 ` Richard Purdie
2019-02-28 15:30 ` Jean-Christian de Rivaz
2019-03-02 18:38 ` Randy MacLeod
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=20190228051945.GB11051@localhost \
--to=bunk@stusta.de \
--cc=ross.burton@intel.com \
--cc=trini@konsulko.com \
--cc=yocto@yoctoproject.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.