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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070712231645.GY11166@waste.org>
Date:	Thu, 12 Jul 2007 18:16:45 -0500
From:	Matt Mackall <mpm@...enic.com>
To:	Rob Landley <rob@...dley.net>
Cc:	Roman Zippel <zippel@...ux-m68k.org>, linux-kernel@...r.kernel.org,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH] Start to genericize kconfig for use by other projects.

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.

-- 
Mathematics is the supreme nostalgia of our time.
-
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/