[Xorg] CVS HEAD -- ftfuncs.c:931: error: structure has no membernamed `find_sbit_image'

[Egbert Eich]

Keith Packard writes:
 > 
 > Around 6 o'clock on Jul 30, Roland Mainz wrote:

 > Shipping code which has known build regressions in its default
 > configuration is not acceptable.
 > 
 > Forcing people to use a static copy of a soon-to-be-outdated version of
 > FreeType is similarly unacceptable.

The above arguments don't seem to fit together:
One would expect that people interested in latest-and-greatest code
already have FreeType 2.1.8 installed.
People still using an older version are not expected to update to
a version higher than 2.1.8 later if they are not willing to update
to 2.1.8 now. For these the internally shipped version 2.1.8 would
give them the opportunity to use newer code than what they already 
have.

 > 
 > Please fix the code or I will recommend that the whole patch be backed out.
 >  I would fix it myself, but I'm afraid I will get it wrong as I have no
 > applications which I can easily configure to use core fonts.
 > 
Keith, 

it is appropriate to ask Chisato to #ifdef his code on the version of
FreeType however I feel it is not fair to threaten with the deletion
of his code.

Chisato Yamaushi's code patch created a dependecy to FreeType 2.1.8. 
The inclusion of this code was a prerequisite for dropping the XTT
font renderer. 

When we did the 6.7 release we created dependencies to FreeType 2.1.7
although most people had older versions of freetype installed. Still we
decided to turn off the use of 'internal' version of FreeType we 
ship by default (at least on those platforms that usually ship FreeType)
for the arguments you stated above. Instead we decided to document 
this dependency in the release notes and offer people to enable the 
internal version of freetype as quick a workaround.

The majority of people active on this mailing list may not be affected 
by the deletion of this patch. However a considerable group of people
would suffer tremendously. This group is largely silent on this forum.
This silence however does not proof that this group does not exist.

Not allowing these people to include their code with the same arguments 
that have worked for us in a previous release and even threatening with 
the removal of their code is inappropriate.


Egbert.