On Thu, Sep 3, 2015 at 9:11 AM, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > On Wed, 2015-09-02 at 16:23 -0300, Otavio Salvador wrote: >> On Wed, Sep 2, 2015 at 4:09 PM, Randy MacLeod >> <randy.macl...@windriver.com> wrote: >> > On 2015-09-02 11:55 AM, Otavio Salvador wrote: >> >> >> >> On Tue, Sep 1, 2015 at 6:34 PM, Joe Slater <jsla...@windriver.com> wrote: >> >>> >> >>> Implements ifup and ifdown. >> >>> >> >>> Copied from https://github.com/WindRiver-OpenSourceLabs/meta-overc.git >> >>> as of commit aa89eebffe06e4aa04701eae9691cb3049cbaef9. >> >>> >> >>> Signed-off-by: Joe Slater <jsla...@windriver.com> >> >> >> >> >> >> I think this belongs to meta-networking. Also, what this one provides >> >> which is not provided by the busybox one? >> > >> > We're trying to make busybox optional for larger systems >> > that want to only use the full-featured/bloated packages. >> > It's not a large tax to carry busybox in a 50+ MB image but >> > it would be nice to not require it. >> >> I see; I still think this belongs to meta-networking as it will allow >> this to be done however won't add new recipes in core. >> >> If many people start to use this, we can move this to core. > > To put this another way, I think it is probably reasonable that we > should be able to build an image from OE-Core with basic functionality > like networking without busybox?
That is the point; this were not in meta-networking and noone missed it until now. Moving this to oe-core straight seems overkill. I think moving this to meta-networking is right and if many people use it, oe-core is next step. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
