Hi Oliver
I don't think this is easier: someone with rather deep knowledge of the
OOo startup would have to provide C++ code to be run during first
startup, while shared packages "only" affect packaging.
No. The "only" problem would be rights
the purpose of this is to register Extensions by launching a unopkg over
the <OOo>/share/uno_packages directory
Obviously, i'm opened to discussions :-)
My concern is to make things easy to enrich OOo
What is not yet clear to me is: do you want extensions to be part of the
packaging process or do you want to be able to dynamically add "native
packed extensions" to an OOo installation set after instsetoo_native has
completed ?
Extensions, as reviewed and accepted, would be part of the packaging
process. No "dynamic" post-building extensions definition
The purpose is tointegrate popular Extensions into OOo so that users do
not have to install them
Laurent
--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org
Indesko >> http://www.indesko.com
Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org
Livre "Programmation OpenOffice.org", Eyrolles 2004
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
