On Tue, Feb 28, 2012 at 03:26:16PM +0000, Daniel P. Berrange wrote: > The new OsinfoInstallConfig class provides the configurable parameters > that can be subsituted into the install scripts. This includes hardware > properties (architecture), localization (timezone, language, keyboard), > admin details (password), user details (login name, password, autologin > flag, etc) and registration details (product key, user login & password). One of the challenges of this is that the values for certain config fields are essentially "enums", but each OS uses its own strings or numbers. eg, timezone, language & keyboard are all essentially enums. With this current patchset the app/user needs to provide the config values for these fields in the OS-specific format. My intention is that we define a set of standardized strings can be be used, which will get auto-converted to the native strings. eg, // Use the Windows specific format: osinfo_install_config_set_l10n_keyboard(config, "United Kingdom"); // Use the libosinfo standard format osinfo_install_config_set_l10n_keyboard(config, "libosinfo:uk"); // Or equivalently: osinfo_install_config_set_l10n_keyboard(config, OSINFO_INSTALL_CONFIG_L10N_KEYBOARD_UK); Again I intend for the mapping data to be part of the database, eg <mapping id="http://microsoft.com/mapping/keyboard";> <key name="uk">United Kingdom</key> ... </mapping> And then you can reference this from the <install-script> elements <install-script id="http://microsoft.com/install/sif";> <mapping config="l10n-keyboard" id="http://microsoft.com/mapping/keyboard"/> .... </install-script> <install-script id="http://microsoft.com/install/unattend";> <mapping config="l10n-keyboard" id="http://microsoft.com/mapping/keyboard"/> .... </install-script> Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
