To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52026
                  Issue #:|52026
                  Summary:|Remove private copy of libfreetype.so.6 for Linux ?
                Component:|gsl
                  Version:|680m115
                 Platform:|All
                      URL:|
               OS/Version:|Linux
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|hdu
              Reported by:|obr





------- Additional comments from [EMAIL PROTECTED] Fri Jul 15 05:20:10 -0700 
2005 -------
The purpose of this issue is to discuss whether libfreetype.so.6 can be treated
as runtime prerequisite and how this can get enforced by the packaging.

Unfortunatly linux vendors tend to name their packages (RPMs) differently, so a
direct package dependency can not be set.

The AutoPreReq mechanisms of RPM, which record the SONAME(s) of all dependant
libraries, are turned off in the OOo build environment (for performance &
baseline conformance reasons), so the only way to fix this in the OOo RPMs seems
to be to provide a special "find-requires" script as already done for the
gnome-integration package. 

The SONAME for a shared library can be determined using objdump -p.

---------------------------------------------------------------------
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]

Reply via email to