Apache OpenOffice (AOO) Bugzilla – Issue 6485
[RFE] OOo should allow auto registration of mozilla components at setup
Last modified: 2013-08-07 15:45:41 UTC
To support the integration of mozilla address books plus LDAP and Outlook/Outlook Express integration with OOo, we ship a limited number of mozilla components. We also ship the mozilla component registry for these components [component.reg] only and the related file xpti.dat in the OOo installation/program/components. These two files can be automatically generated. We ship them to ensure that during a networked installation, we do not have problems about write access to a networked directory. An alternative strategy would allow us to create these files as part of the installation process. To achieve this, we would simply need a program which would be called as part of the installation process and pass the OOo installation program directory as a parameter to this utility. This strategy would ensure that that we have an automated process for these files and remove the need to ship two files. I hope to post such a program here so that we can evaluate whether this would be a better alternative to our existing process.
Created attachment 2287 [details] sample test source program to perform auto registration
Created attachment 2288 [details] sample Makefile to compile mozabreg.cpp in mozilla/embedding/tests/apitest
Note: for this sample program to run successfully, we need to include the mozilla component libembedcomponents.so
Hi Frank, I think this is a good idea and reduces the risk of breakage. We should check the effort to integrate it into the setup. - Dirk
setting target milestone to OOo 2.0
adding [RFE] to the summary
fs->wind,gilbert: found another AB issue lingering in my intray ...
It may improve the OO. Anyway, I do not see any big benifits we can make of it. It seems we only can reduce two files when shipping, but we have to write a new program and *shipped* it with OO setup program and get some extra risk of crashing on this new install program. I prefer that we creat these two register files when building and ship them with SO/OO, if they can work well under all kind of installation.
I agree that the benefits wouldn't be outstanding, so this isn't really a too important issue. Perhaps it's even that a program for doing the registration is bigger than the files themself. Lowering prio to 4.
change subcomponent to 'none'
Migrate to a new account for security reasons.
Closing this in agreement with Wind. We don't think that it's worth the effort, the more since OOo 2.0 will ship with native installers, where it becomes extremly difficult to run own programs during setup, which would do the registration.
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew