Le 5 juin 11 à 10:09, eric b a écrit :
Hi,
First over all, I'm not a native speaker, but I think I can answer.
Apologies if I'm off topic, this thread is extremely difficult to
follow.
Le 5 juin 11 à 09:41, Dennis E. Hamilton a écrit :
I was thinking about binary-only components such as a linker
library or shared library that was under a non-Apache license but
that needed to be included in deployments of OpenOffice.org.
As builder / dev since years in OOo, we separated
- build dependencies : the builder MUST install something to make
the build possible.
- install dependencies : the user must install something to be sure
OpenOffice.org will launch and work correctly
I suppose we are talking about the second one.
If in this case, and if this can be helpfull for you, the policy
for external code was handled by external project -> http://
external.openoffice.org/
Martin Hollmichel (Sun / Oracle employee the last time I've heard
of) is IMHO the one to be contated for further information.
Apologies, the most up to date information is here : http://
wiki.services.openoffice.org/wiki/External/Modules (the previous
link looks outdated)
Regards,
Eric Bachard
--
qɔᴉɹə
Education Project:
http://wiki.services.openoffice.org/wiki/Education_Project
Projet OOo4Kids : http://wiki.ooo4kids.org/index.php/Main_Page
L'association EducOOo : http://www.educoo.org
Blog : http://eric.bachard.org/news
