To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=65521
------- Additional comments from [EMAIL PROTECTED] Mon Sep 25 02:41:57 -0700
2006 -------
simonbr:
> So would it be a good idea to reopen this issue?
This issue is open ;-)
> > what did 109927 say?
>
> Something along the lines of issue 52025 and issue 52026. If a
> system library is available it violates some policy if a private
> version of the library is used.
Well - the problem is detecting if the system library is any good for what
we want I think; I imagine we can only do that by dlopening it and having a poke
around inside.
Luckily the only solution for the licensing problems inherent in:
> * This could be fixed by statically linking the private libfreetype into VCL.
Is to dlopen it :-)
I think the right solution for the longer term is two-fold:
* re-vector all fontconfig calls via an abstract dlopen interface
* rename the internal libfreetype.so.<N> to 'libstarfreetype.so.<N>'
or somesuch [ ultimately StarOffice / these multi-distro builds are
the only consumer.
---------------------------------------------------------------------
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]
