Rich wrote:...
but what about migrating to another machine ?
User configuration is stored in a limited set of files. To migrate stuff to another machine you could simply copy up all relevant files to the
and this exactly is the problem... configuration options are scattered. user must know which files must be copied. file ownership problems might bite user.
other machine. For the configuration settings database there even is a (commandline) tool that allows importing configuration files into an existing configuration database, which will import single settings and leave existing settings in the destination installation unchanged otherwise.
i found configimport.bin - but somehow i'm unable to find detailed information about it's exact function, functionality. especially i have no idea what data it expects as an input.
can this tool be used for configuration export ?
...
For StarOffice there even is a tool where you can setup preferences in a central directory (using a webbased frontend) and have them apply those to all your instances or even to groups of people or machines.
well, it's for staroffice... what do we get ?
how possible would it be to create such a functionality that oo.org would read a single file for configuration items and all settings that would be specified in this file would take precedence over all other places of settings ? in this case user could create such a file and just copy this single file over to another oo.org installation. it would be a single file, minimal screwup possibility, easy to edit etc.
Ciao, Joerg
-- Rich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
