From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Joe Slater <jslater@windriver.com>
Subject: Re: [PATCH 1/2] ifupdown: import recipe
Date: Thu, 03 Sep 2015 13:11:28 +0100 [thread overview]
Message-ID: <1441282288.24871.113.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpx4niWDNDy4t2SUf7xwz5ShoZMsivtM6_qA3o-kBo5AA@mail.gmail.com>
On Wed, 2015-09-02 at 16:23 -0300, Otavio Salvador wrote:
> On Wed, Sep 2, 2015 at 4:09 PM, Randy MacLeod
> <randy.macleod@windriver.com> wrote:
> > On 2015-09-02 11:55 AM, Otavio Salvador wrote:
> >>
> >> On Tue, Sep 1, 2015 at 6:34 PM, Joe Slater <jslater@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 <jslater@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?
Cheers,
Richard
next prev parent reply other threads:[~2015-09-03 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 21:34 [PATCH 0/2] add ifupdown Joe Slater
2015-09-01 21:34 ` [PATCH 1/2] ifupdown: import recipe Joe Slater
2015-09-02 15:55 ` Otavio Salvador
2015-09-02 19:09 ` Randy MacLeod
2015-09-02 19:23 ` Otavio Salvador
2015-09-03 12:11 ` Richard Purdie [this message]
2015-09-03 12:15 ` Otavio Salvador
2015-09-03 12:20 ` Bruce Ashfield
2015-09-03 20:22 ` Khem Raj
2015-09-03 20:27 ` Richard Purdie
2015-09-03 20:32 ` Otavio Salvador
2015-09-03 21:02 ` Bruce Ashfield
2015-09-03 21:24 ` Khem Raj
2015-09-03 21:38 ` Bruce Ashfield
2015-09-03 21:15 ` Khem Raj
2015-09-03 21:39 ` Richard Purdie
2015-09-04 1:12 ` Slater, Joseph
2015-09-03 21:28 ` Phil Blundell
2015-09-03 21:46 ` Khem Raj
2015-09-03 12:32 ` Jack Mitchell
2015-09-01 21:34 ` [PATCH 2/2] ifupdown: create alternative links Joe Slater
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 12:24 [PATCH 1/2] ifupdown: import recipe Andrew Shadura
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=1441282288.24871.113.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jslater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox