From: Darren Hart <dvhart@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: RFC: User configurable recipe features
Date: Tue, 11 Oct 2011 09:06:24 -0700 [thread overview]
Message-ID: <4E946980.3000001@linux.intel.com> (raw)
In-Reply-To: <CAEsOVNc8=_PSwh29Dw8TMDHd5biqpaXQo6Ce_n4kkJ4KdAAsQg@mail.gmail.com>
On 10/11/2011 08:53 AM, McClintock Matthew-B29882 wrote:
> On Mon, Oct 10, 2011 at 1:41 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> I would want this to affect linux-yocto-tiny by dropping the vt.cfg and
>> inet.cfg fragments from the SRC_URI (or from the .scc descriptor files
>> assembled by the linux-yocto meta indrastructure).
>>
>> Busybox would need a similar configuration mechanism, and would also
>> need to add a "no-vt-support.patch" patch to the SRC_URI to avoid a
>> bug/oversight in the busybox init routine.
>
> Just chiming in on this point - I think busybox will need something
> very similar to config fragments. It has a lot of functionality that
> should be configurable.
Agreed, and it can probably use a very similar mechanism to what I've
been working to get into the upstream Linux kernel.
I've been looking at the uclibc recipe configuration functions. It looks
like it tries to solve a similar problem using feature lists and
programatically modifying the .config. More research needed there...
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-10-11 16:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 18:41 RFC: User configurable recipe features Darren Hart
2011-10-11 15:53 ` McClintock Matthew-B29882
2011-10-11 16:06 ` Darren Hart [this message]
2011-10-11 22:15 ` Richard Purdie
2011-10-11 23:51 ` Khem Raj
2011-10-12 0:18 ` Philip Balister
2011-10-12 15:41 ` Darren Hart
2011-10-12 15:47 ` Koen Kooi
2011-10-12 15:52 ` Paul Eggleton
2011-10-12 16:49 ` Darren Hart
2011-10-12 15:40 ` Darren Hart
2011-10-11 23:49 ` Tim Bird
2011-10-12 15:55 ` Darren Hart
2011-10-12 18:44 ` Khem Raj
2011-10-12 19:30 ` Koen Kooi
2011-10-12 19:32 ` Khem Raj
2011-10-12 20:15 ` Darren Hart
2011-10-12 19:13 ` Tim Bird
2011-10-12 16:59 ` Darren Hart
2011-10-12 17:19 ` Tim Bird
2011-10-12 19:22 ` William Mills
2011-10-13 8:30 ` Jack Mitchell
2011-10-13 18:33 ` William Mills
2011-10-13 20:50 ` Khem Raj
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=4E946980.3000001@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=B29882@freescale.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.