Aditya Pandey wrote:
Hi

I have been able to use configimport command for creating/installing a schema
I have created for my addin to OpenOffice.


You don't need configimport to install a schema (xcs) or xcu file. unopkg installs them in a private location.

When I try to uninstall the addin, the .xcs (schema) file is removed by unopkg
utility, but the data file (.xcu) file and cache file (.dat) files are still there.


unopkg can remove only the installed files from the private location managed by unopkg.

The files under $(userdata)/user/registry are created by the office when the configuration data you installed is accessed (cache/*.dat) or when configuration settings are modified by (or for) the user (*.xcu under data/).

unopkg doesn't know about these files and if you install your package as shared package (using the --shared option to unopkg), then there could be an instance of them for every user - potentially an unlimited number.

Because of this these files can't be uninstalled. But they should do no harm (other than consume disk space). You can't access the data through OOo configuration intrefaces. And when the package is installed again, the user will find their personal settings from last time.

I tried configimport options to remove these files, but could not do it? Am I
missing something?


Configimport can't possibly do that.

The only possibility would be writing a configcleanup program that removes xcu and dat files for which there is no corresponding schema.Then every user would have to run that program.

But that program hasn't even been written yet. You can file an RFE, but it won't get a high priority atm.

Ciao, Joerg

--
Joerg Barfurth              Sun Microsystems - Desktop - Hamburg
>>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<<
Software Engineer                         [EMAIL PROTECTED]
OpenOffice.org Configuration          http://util.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to