On Thu, Feb 28, 2019 at 02:27:37PM +0000, Richard Purdie wrote: > On Thu, 2019-02-28 at 12:05 +0000, Burton, Ross wrote: > > On Thu, 28 Feb 2019 at 05:20, Adrian Bunk <b...@stusta.de> wrote: > > > > 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). > > > > But a "close enough" packagegroup in core would be a good starting > > point. > > > > > > 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. > > > > Good point well made. > > > > 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. > > > > I thought we had some other editor in core, but can't see one. Worse > > case we still use busybox for its vi... :) > > This could be an argument for pulling a small number of things into OE- > Core too...
Moving the vim recipe (which doesn't have further depends) over and then putting VIRTUAL-RUNTIME_vim and ?= "vim-tiny" in this packagegroup should be flexible enough, yes? -- Tom
signature.asc
Description: PGP signature
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
