Hi all
Extensions popularity is growing. One will soon end with the request on
including popular extensions within OOo at installation time
(i've already 2 - DicOOo and Xray)
There is 2 options :
1. scratch the extensions and reinclude it into sources
2. use the extension and deploy it at the end of OOo installation
1 is non sense to me as we asked user to do extensions and then break it.
Moreover, who will do the job ? not the extension creator who generally
do not have the skills or time to dig into OOo build mechanism
So, 'regular' devs will have to do, and they already do not have any
free time
So solution 2 sound the best logical to me
How to perform this ? is it possible to launch post-install scripts (i
heard that some plateform had problem)
If uno packages are copied at installation time in /share/uno_packages,
, it is only a matter of launching a command line unopkg -s
If they are deployed at user level (inefficient imho), one can launch
this registering process at first start
btw, there remain the license acceptation, but this can be postponed if
we consider the acceptation on the OOo one is also good
only libcence compatible extensions will be packaged though
So, please do you have any comment and action plan to make this possible ?
I cross posted this message top gather widely the feelings. Sorry for
that. I think further discussion can occur on [EMAIL PROTECTED] mailing list
Thanks
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]
