[xorg-bugzilla-noise] [Bug 556] RFE: Update FreeType2 version in xc/extras/Freetype2 to V2.1.8...

[bugzilla-daemon at pdx.freedesktop.org]

http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=556





------- Additional Comments From roland.mainz at nrubsig.org  2004-05-06 04:37 -------
Egbert Eich wrote:
> Roland Mainz wrote:
> > Uhm... this is usually the way how moz.org does the job - the patch is 
> > stored in
> > bugzilla for review/approval and checked-in as-is. Nothing in the main 
> > branches goes "in" without being stored in bugzilla first.
>
> Right. But you were pulling in the freetype2 2.1.8 bits. These things should 
> go in unchanged. If at all we need to work around problems from outside. 
> Changing the freetype code in our tree means we have to tack our changes in 
> future versions. XFree86 seems to do this sometimes - but it is crazy. 
> freetype should not even have to be in the tree and we are moving to a 
> situation where it doesn't have to be. 
> I've checked for differences to freetype2 2.1.8: I found a change in the
> ftconfig.h header which was related to CHAR_BITS. I've reverted this and added 
> a patch to another place to take care of the problem. 

I found the difference yesterday... my fault... but I was preparing a patch for
the Freetype.org CVS to include that fix... is that no longer needed now ?

> > Uhm... are there any bugzilla bugs which describe the "kludges" ?
> No, unfortunately not. Today I worked a little bit more on the freetype issue
> and found some other symbol problems. I will make a separate entry to bugzilla
> for this.
> I may also delete the static freetype module build so that the freetype module 
> that gets used will be an .so which can link against a system supplied 
> freetype library.

Erm... will that mean that I cannot build a Xserver with a statically linked
Freetype module and Freetype library ? Remember that our own Xprint.org releases
always linked Freetype statically for stability and maintaince reasons... and it
will take a couple of years until all distributions have adopted at least
FreeType 2.1.8. Please do not do that...



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.