From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NZhDd-0004du-Rx
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 03:56:17 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NZhDZ-0004bB-0P
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 03:56:17 -0500
Received: from [199.232.76.173] (port=46180 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NZhDY-0004ar-J4
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 03:56:12 -0500
Received: from mx1.redhat.com ([209.132.183.28]:17835)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NZhDV-000408-MU
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 03:56:10 -0500
Message-ID: <4B5EAE25.7050507@redhat.com>
Date: Tue, 26 Jan 2010 10:56:05 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 1/3] Support --sysconfdir in configure
	to specify path to configuration files (v3)
References: <1264342938-7363-1-git-send-email-aliguori@us.ibm.com>	<1264342938-7363-2-git-send-email-aliguori@us.ibm.com>	<hjhme7$ht7$1@ger.gmane.org>
	<4B5C65D7.5040304@codemonkey.ws> <4B5DADFE.8050606@redhat.com>
	<4B5E07B4.4090205@redhat.com>
In-Reply-To: <4B5E07B4.4090205@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org

On 01/25/2010 11:05 PM, Paolo Bonzini wrote:
>
>>>> I'm not sure about the choice for Windows. Do we want possibly a
>>>> dozen of .conf files all in the same directory as the binaries, or
>>>> maybe it's better to set sysconfdir = ${prefix}/conf,
>>>> confdir=${sysconfdir} on Windows?
>>>
>>> I honestly don't know. What's the normal thing to do with Windows?
>>
>> The registry, I think.
>
> The registry would be used indeed to get the path or to override 
> defaults.  However, what would be the default value (written in the 
> registry by the installer, or used by the program if the registry 
> value is absent)?

You could use the registry to hold the defaults, not a path to the defaults.

-- 
error compiling committee.c: too many arguments to function