From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 0/4] Allow schedulers to be selectable through Kconfig Date: Thu, 7 Jan 2016 15:31:23 +0000 Message-ID: <1452180683.21055.247.camel@citrix.com> References: <1450385974-12732-1-git-send-email-jonathan.creekmore@gmail.com> <1450435531.4053.196.camel@citrix.com> <567448E9.2030702@cardoe.com> <1452091541.21055.58.camel@citrix.com> <568E864F02000078000C4731@prv-mh.provo.novell.com> <1452178843.21055.230.camel@citrix.com> <568E81DF.5060301@cardoe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aHCXD-0007fD-Nn for xen-devel@lists.xenproject.org; Thu, 07 Jan 2016 15:31:31 +0000 In-Reply-To: <568E81DF.5060301@cardoe.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Doug Goldstein , Jan Beulich Cc: Ian Jackson , Jonathan Creekmore , Keir Fraser , xen-devel@lists.xenproject.org, Tim Deegan List-Id: xen-devel@lists.xenproject.org On Thu, 2016-01-07 at 09:18 -0600, Doug Goldstein wrote: > > > With me asking for that option to not have a visible prompt by > > > default, > > > but nevertheless being settable. I do realize that this may not be > > > possible with the current kconfig tool, but that's imo the only way > > > to > > > keep people from playing with expert options just because they see > > > there's a prompt. No textual warning will help this, I'm afraid. > > > > While I have reasonably strong opinions about this issue, I do not > > think > > they warrant forking Kconfig over. > > > > With a suitably strong wording IMHO we have covered ourselves > > sufficiently. > > > > Ian. > > > > So Jonathan and I have been messing with the hidden option behind a > non-menu option (e.g. environment variable). The only way we can get it > to work is to require the environment variable to be passed at > configuration time and at build time and I doubt you'd want the steps to > be "CONFIG_EXPERT=n make menuconfig && CONFIG_EXPERT=n make" to build > Xen. We'll play with this some more if that's desired but given Ian's > response I don't know if it is. You mean it has to be given as either =n or =y i.e. it has no default? I don't think we can live with that indeed. Ian.