From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Joe Slater <jslater@windriver.com>,
Otavio Salvador <otavio.salvador@ossystems.com.br>
Subject: Re: [PATCH 1/2] ifupdown: import recipe
Date: Thu, 03 Sep 2015 21:27:04 +0100 [thread overview]
Message-ID: <1441312024.24871.135.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sp=Hiwt=oYfFy8Mhj4TMXj3x3Tykmg6mNLLtyEXV+TVwQ@mail.gmail.com>
On Thu, 2015-09-03 at 13:22 -0700, Khem Raj wrote:
> On Thu, Sep 3, 2015 at 5:20 AM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> >> 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's what I'd support. If everything you need for the functionality with busy
> > box is in oe-core, to me, it doesn't make sense to go outside core to get that
> > same functionality without busybox.
>
> irrespective of this change. I see yet another configuration with this
> into OE-core, overall OE-Core should get smaller
> and case does not sound convincing to me. You dont want to use busybox
> in a fairly large image which has other GPLv2 software in
> it. Thats fine but doesnt look like a common usecase to me
Nobody mentioned GPLv2, that isn't relevant here.
I have heard OE being dismissed since it can't produce an image without
busybox in it. The implication is we can't build "big" Linux, only small
embedded things. The pieces we need busybox for are tiny and should be
easy to replace (like this does).
So I can see a fairly compelling argument for OE-Core to be able to
generate a busybox free image with standard functionality just from a PR
perspective. From what I gather we have people willing to test and
maintain it too...
Cheers,
Richard
next prev parent reply other threads:[~2015-09-03 20:27 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
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 [this message]
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=1441312024.24871.135.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jslater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=raj.khem@gmail.com \
/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