On 02/12/2010, at 12:46 AM, Daniel P. Berrange wrote: > On Wed, Dec 01, 2010 at 09:19:30PM +1100, Justin Clift wrote: >> On 01/12/2010, at 8:35 PM, Osier Yang wrote: >>> Should we add these new preferences(if they are really neccessary) >>> in qemu.conf? or create new config file, e.g. The approch Justin >>> raised up an approch before: >>> http://www.redhat.com/archives/libvir-list/2010-November/msg00651.html >>> >>> Though for Justin's approch, IMHO we'd better also to provide a >>> default config file, e.g. "/etc/libvirt/client.conf". >>> >>> Any feedback is welcomed, thanks >> >> When thinking about this more, three levels of preference can be found in >> other applications, and _might_ be the right approach for us to take as well. > > Management of preferences belongs in application code, rather than > libvirt. Library APIs need to have standard, predictable behaviour > that apps can rely on in any deployment. We don't want that being > changed globally for all applications by config files. > > Even if apps do want configuration data, we can't assume they want the > data stored in configuration files. Any current GTK application will > use GConf for any configuration, or in the future GSettings which > has pluggable backends per OS platform. Good point. Its a per client thing, and each client would store the preferences in the way that makes best sense for it. GConf for GTK things, something else for KDE, and a virsh appropriate approach for that if/when we get around to it. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list