To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105332 Issue #|105332 Summary|Provide dynamic libs instead of static ones Component|framework Version|DEV300m59 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|hr Reported by|jl
------- Additional comments from [email protected] Thu Sep 24 14:00:25 +0000 2009 ------- The module libxmls builds static libraries on non-Windows platforms. The argument was (quoting cmc's entry from cws jl135_nss): ""I am investigating who did this [make the unix libs static] to us." I did that a year or two ago, makes OOo smaller and removes the libxmlsec .so from rpm "autoprovides" which was confusing packaging dependency systems into installing OpenOffice.org when another application was linked to "libxmlsec" which then couldn't work because the OOo libxmlsec is an incompatibly modified version of the original" My arguments for dynamic libraries are: 1. The static libraries introduced a build dependency. Changing code in libxmlsec makes it necessary to build all other modules which make use of libxmlsec. This is currently only xmlsecurity. However, this can be overlooked easily if one does not build from ground up. 2. Saving space is nice but I would not regard this as crucial. Also this saving might get lost if other modules also need to link against this static library. 3. I think it handy to just being able to compare file sizes to see if a library changed in a particular build. Particularly if we introduce an important fix and there is no test case available. In this case the QA time has a hard time to verify the fix. To see that a particular libraries has an obvious changed size would certainly help. 4. OOo (vanilla) contains a lot of external libraries, which can also be on the system (berkely, nss). Other applications which use those libraries have potentially the same problem as those who use libxml and accidentally get those from OOo. 5. OOo (vanilla) has the external libraries in its installation, for example /opt/OpenOffice.org/openoffice.org 3/basis/program Other programs should not being able to use libraries from that place unless they do something really weird. I do not know much about packaging therefore I cannot really find arguments regarding rpm "autoprovides". However, if this would be an argument then this would affect all other external modules as well. Although the current situation (having static libs), fixes this problem, I think it introduced others which also cannot be neglected. Therefore I am in favor of changing libxmlsec to provide dynamic libraries again. Let me cc some colleagues, to get some more opinions. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
