linux-kernel - Re: [PATCH] Allow kconfig to accept overrides

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]

Date:	Tue, 16 Oct 2007 16:44:30 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	Rob Landley <rob@...dley.net>, zippel@...ux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	randy.dunlap@...cle.com
Subject: Re: [PATCH] Allow kconfig to accept overrides

Hi Sam,

On Oct 16 2007 06:29, Sam Ravnborg wrote:
>On Fri, Oct 12, 2007 at 11:44:08PM +0200, Jan Engelhardt wrote:
>> 
>> Allow config variables in .config to override earlier ones in the same
>> file. In other words,
>> 
>> 	# CONFIG_SECURITY is not defined
>> 	CONFIG_SECURITY=y
>> 
>> will activate it. This makes it a bit easier to do
>> 
>> 	(cat original-config myconfig myconfig2 ... >.config)
>> 
>> and run menuconfig as expected.
>
>
>How far is this from the miniconfig functionality?
>Is it the same or can we achieve the miniconfig support
>by extending Jan's patch?
>
>See: http://lkml.org/lkml/2007/10/12/391


miniconfig actually does something completely different as far as I
understand: miniconfig creates a minimal config that does not contain
default choices for CONFIG_ files, while the patch that I was trying
to submit here allows to override entries in a .config by just
appending them to the file. I already have a miniconfig, so to speak,
and want to merge it with the previous .config so as to produce a
fullconfig. (Something like the exact opposite)


thanks,
Jan
-
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/