Re: [dev] drop configimport?
Stephan Bergmann wrote: Are there any objections against dropping the configimport tool from OOo 3.0? It seems that its typical uses (if any) can also be achieved with other means (see http://www.openoffice.org/issues/show_bug.cgi?id=87512), so we can lose some weight here. done (dropped) -Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] drop configimport?
Rene Engelhard wrote: Hi, Thorsten Behrens wrote: On Fri, Mar 28, 2008 at 09:55:39AM +0100, Stephan Bergmann wrote: Are there any objections against dropping the configimport tool from OOo 3.0? It seems that its typical uses (if any) can also be achieved with other means [...] Hi Stephan, r while I don't think you can get away with simply copying files, it's true that there are other mechanisms to achieve config import - e.g. the xcu fragments one can put into oxts. So, yep, sounds reasonable to drop it. I disagree. it's unneeded overhead to have to create a oxt for this for system administrators. They should be able to touch the configs directly. The only real way for this (if ou don't want to do the config file completely new, but just change a node) is configimport. For overrides, you can put additional oxt files into the share/registry/module tree (as has been discussed in the comments at http://www.openoffice.org/issues/show_bug.cgi?id=87512). Would not that be enough for you? Please don't drop it. sb: Any reason why you want to drop it? Cutting costs: We have too much code, with too many artifacts generated from it. That costs. Heavily. (Plus, since DEV300m4, configimport is broken, and the easiest way to fix it is to drop it...) -Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] drop configimport?
Hi, Thorsten Behrens wrote: On Fri, Mar 28, 2008 at 09:55:39AM +0100, Stephan Bergmann wrote: Are there any objections against dropping the configimport tool from OOo 3.0? It seems that its typical uses (if any) can also be achieved with other means [...] Hi Stephan, r while I don't think you can get away with simply copying files, it's true that there are other mechanisms to achieve config import - e.g. the xcu fragments one can put into oxts. So, yep, sounds reasonable to drop it. I disagree. it's unneeded overhead to have to create a oxt for this for system administrators. They should be able to touch the configs directly. The only real way for this (if ou don't want to do the config file completely new, but just change a node) is configimport. Please don't drop it. sb: Any reason why you want to drop it? Regards, Ree - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] drop configimport?
Are there any objections against dropping the configimport tool from OOo 3.0? It seems that its typical uses (if any) can also be achieved with other means (see http://www.openoffice.org/issues/show_bug.cgi?id=87512), so we can lose some weight here. -Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] drop configimport?
On Fri, Mar 28, 2008 at 09:55:39AM +0100, Stephan Bergmann wrote: Are there any objections against dropping the configimport tool from OOo 3.0? It seems that its typical uses (if any) can also be achieved with other means [...] Hi Stephan, while I don't think you can get away with simply copying files, it's true that there are other mechanisms to achieve config import - e.g. the xcu fragments one can put into oxts. So, yep, sounds reasonable to drop it. Cheers, -- Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]