linux-kernel - Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II

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:	Thu, 3 May 2007 22:53:03 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Trent Piepho <xyzzy@...akeasy.org>
cc:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	v4l-dvb maintainer list <v4l-dvb-maintainer@...uxtv.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II -
 DVB


On May 3 2007 13:39, Trent Piepho wrote:
>
>> >The point rised by Trent is that, currently, this is not prepared to
>> >handle the "menuconfig" and "if/endif" tags.
>
>BTW, I've now fixed this.
>
>Jan, have you looked at the effect these changes have when using xconfig, and
>not just menuconfig?

"The mouse is used to point at the xterm you want to type in."

So, sorry, no, I did not. However, Stefan notes his experience
with some earlier patches with [xg]config:
http://lkml.org/lkml/2007/4/10/326

For you, I installed qt3-devel/libglade2-devel on my machine
and ran it in [xg]config. 

>While your changes make menuconfig better, they have nearly opposite effect on
>xconfig.
>
>xconfig has the menu tree display in the left panel, where one can see the
>overall layout of the menu tree and jump directly to any menu (even one
>multiple levels deep).  All the menuconfigs that used to be menus don't show
>up here anymore.

That seems very much like a bug^Wmissing feature in [xg]config's
"Split View". It does work in Single View and Tree View.

>It looks like your changes are going in, so I suppose the solution is to
>improve the way xconfig handles "menuconfig".
>[...]
>The reason is that a frontend would easily be able to understand the coupling
>between the "menuconfig XXXX" and the "if XXXX".  It will make it easier for
>the frontend to see that all the options are inside and controlled by the
>enclosing menuconfig.

It works a bit different than 'menu'. An object will be put into a
menuconfig-menu IFF it has a depends on the menuconfig item.
This is different from menu-menus, which have "sort of" an
implicit "if/endif" block.


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/