Re: [PATCH] Start to genericize kconfig for use by other projects.

[Rob Landley]

On Thursday 12 July 2007 7:16:45 pm Matt Mackall wrote:
> On Thu, Jul 12, 2007 at 02:44:18PM -0400, Rob Landley wrote:
> > On Thursday 12 July 2007 12:28:39 pm Roman Zippel wrote:
> > > Hi,
> > >
> > > On Wed, 11 Jul 2007, Rob Landley wrote:
> > > > Replace name "Linux Kernel" in menuconfig with a macro (defaulting to
> > > > "Linux Kernel" if not -Ddefined by the makefile), and remove a few
> > > > unnecessary occurrences of "kernel" in pop-up text.
> > >
> > > Could you drop the PROJECT_NAME changes for now? The rest looks fine.
> > > I would prefer if the project would be settable via Kconfig.
> >
> > Are projects likely to grab a common kconfig binary externally, rather
> > than build their own?
>
> Yes.
>
> If you really want to share kconfig, it'd be better to break it off
> into a separately packaged project. For the time being, the kernel
> makefiles can look for it in path, then fall back to its own copy
> which we can eventually drop.

That is _so_ not my call.

Right now, the version in linux-kernel is the master.  I'm not saying that 
should be the case, I'm just saying it is.  That's why I'm pushing patches 
that way rather than recommending anyone else use the version I cleaned up in 
toybox (which is currently fairly standalone).

If somebody wants to break it out and maintain it as a separate project, fine 
with me, just tell me where I should look and where to send patches.  But if 
the linux kernel doesn't actually start _using_ said external version, and 
instead maintains its own, the external version will go the way of libsysfs 
when udev went "a shared library means we include it in our source tree and 
build our own copy".

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/