> - immediately freeze development on the current code base
>
> - perform a massive diff between the content of
> "include/freetype/internal" between the 2.1.10 release and the
> current CVS, and study how we can stub each type, field and
> function defined here.
>
> - do the required modifications, encapsulating each of the "old"
> internals in a configuration macro
> (e.g. FT_CONFIG_OPTION_OLD_INTERNALS)
>
> - test, test, test, on existing installations. Preferabbly ones with
> old releases of fontconfig/libXft/Pango/Qt/etc...
>
> - release something stable as early as possible.
>
> Any comments ?
Sounds good. We should mention in the docs that these steps are
performed only *once*, and that we are not going to maintain those
hacks.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
