[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4CEE90C9.8060607@suse.cz>
Date: Thu, 25 Nov 2010 17:37:29 +0100
From: Michal Marek <mmarek@...e.cz>
To: Arnaud Lacombe <lacombar@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kbuild@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: [PATCH 1/5] [PATCH 1/5] kconfig: Make localmodconfig handle environment
variables
On 25.11.2010 17:21, Arnaud Lacombe wrote:
> Hi,
>
> On Thu, Nov 25, 2010 at 10:45 AM, Michal Marek <mmarek@...e.cz> wrote:
>> What information does localmodconfig need? A list of config options and
>> their computed dependencies and a flag for each option if it has prompt,
>> anything else? So a scripts/kconfig/conf --dump-kconfig that would
>> produce such flat list should suffice, without the complexity of having
>> to build a perl binding first (and would be usable from bash/awk/python
>> scripts as well). What do you think?
>>
> Just as a FYI, the output of zconfdump() does not respect the kconfig
> syntax. I've got some patches to fix that, but I've not been able to
> touch them since a few weeks now.
I'm not saying zconfdump() has to be used or that it has to follow the
kconfig syntax (*), just that a pipe interface between the C kconfig and
a Perl script might be easier to implement and use :-).
(*) Although using a subset of the kconfig syntax would be a good idea
definitely.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists