From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH 1/3] Support --sysconfdir in configure to specify path to configuration files (v3)
Date: Mon, 25 Jan 2010 22:19:45 +0100 [thread overview]
Message-ID: <4B5E0AF1.9060107@redhat.com> (raw)
In-Reply-To: <4B5E09B8.8030809@codemonkey.ws>
On 01/25/2010 10:14 PM, Anthony Liguori wrote:
> On 01/25/2010 03: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)?
>
> ini-style configs are not at all uncommon on Windows. I also don't
> think it's that uncommon to store executables and config files
> side-by-side in a Program Files directory.
Indeed, that's what I'm saying. The registry may hold a path to the
ini files, but you would still have to think of a sane default. You
chose the binaries' directory, fine, that's not a huge deal---someone
who cares about Windows can step up and say what they think.
Paolo
next prev parent reply other threads:[~2010-01-25 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 14:22 [Qemu-devel] [PATCH 0/4] Introduce global config (v3) Anthony Liguori
2010-01-24 14:22 ` [Qemu-devel] [PATCH 1/3] Support --sysconfdir in configure to specify path to configuration files (v3) Anthony Liguori
2010-01-24 14:45 ` [Qemu-devel] " Paolo Bonzini
2010-01-24 15:23 ` Anthony Liguori
2010-01-25 14:43 ` Avi Kivity
2010-01-25 21:05 ` Paolo Bonzini
2010-01-25 21:14 ` Anthony Liguori
2010-01-25 21:19 ` Paolo Bonzini [this message]
2010-01-26 8:56 ` Avi Kivity
2010-01-24 14:22 ` [Qemu-devel] [PATCH 2/3] Move out option lookup into a separate function Anthony Liguori
2010-01-24 14:22 ` [Qemu-devel] [PATCH 3/3] Load global config files by default (v3) Anthony Liguori
2010-01-24 15:00 ` [Qemu-devel] [PATCH 0/4] Introduce global config (v3) Avi Kivity
2010-01-24 15:23 ` Anthony Liguori
2010-01-24 15:04 ` Avi Kivity
2010-01-24 15:10 ` Paolo Bonzini
2010-01-25 11:31 ` Daniel P. Berrange
2010-01-25 13:59 ` Anthony Liguori
2010-01-24 15:25 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B5E0AF1.9060107@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).