On Sun, Apr 24, 2005 22:02:08 PM +0200, Mathias Bauer ([EMAIL PROTECTED]) wrote: > M. Fioretti wrote: > > > So you must not click something in ooo that opens an ooo specific > > program that messes up the system. You must make sure that the > > _native_ installer can present, in its package selection window, > > its own label/submenu of "OO.o extensions", pointing to online > > repositories where the stuff is already in the native format. > > I don't want to discuss the pros and cons of our extension > installer, but I wanted to make clear that the extension installer > in OOo doesn't "mess up the system" because it doesn't even touch > it. It only puts some files into the OOo folder in the users home > directory. I wouldn't call this a mess.
If you have only one PC with only one or two macro of course it doesn't make relevant mess. But how do you install OO.o stuff automatically for multiple users? Or update automatically when a new version of some macro and/or the OS? Or, in the same multiuser/automatic maintenance scenario deal with anything that adds, say, stuff requiring Java, fonts or dictionaries conflicting with those in other apps, etc... Ciao, Marco F. -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ Your education begins where what is called your education is over. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
