Thanks a lot for your feedback!
On Feb 1, 2005, at 1:57 AM, Martin Costabel wrote:
Matthias Neeracher wrote: []Unless I hear objections from the maintainers (I believe Alexander agrees with the 2.1.9 packages, but I have not been able to get ahold of Jeffrey) or other interested parties by next Friday, February 4, I plan to commit the updated packages next weekend.
As you know, I am all in favor of upgrading to a newer freetype2 version, but there are a few things that have to be discussed and decided first.
Hmm, looks like this upgrade is far from ready to go.
Most of them were already discussed here but not yet definitively solved AFAICT.
1. There are still packages that will not build with newer freetype versions because of name changes (e.g. "FTC_Image_Cache" in some versions, "FTC_ImageCache" in others) and maybe other incompatibilities. Mozilla still seems to be in this class. I don't know what to do about this (but see point 3 below).
2. Many configure scripts and other code will break with freetype versions above 2.1.6 because of the gratuitous breakage code introduced at the beginning of freetype.h. We discussed this already, and my suggestion remains to patch the freetype2 package by taking out this breakage code.
The alternative, again, might be to allow multiple versions of freetype.
3. We could think about a possibility to have several versions of freetype2 installed simultaneously. This is non-trivial, because there is no official mechanism provided for this. All known freetype2 dylibs, as incompatible as they are, have an install_name of freetype.6.dylib.
It is doable, though, since we already now have two versions of freetype2, one in /usr/X11R6 and one in /sw/lib. We could create /sw/lib/freetype219 and install everything there, but we would have to change the install_name which is now /sw/lib/libfreetype.6.dylib to /sw/lib/freeype219/lib/libfreetype.6.dylib. I didn't try it, but perhaps building freetype2 instead of --prefix=%p with --prefix=%p/lib/freetype%v would do the trick?
That sounds like a worthwhile approach, and I should give that a try. I'm not sure if freetype219 in the path is the right thing to do, in case later releases turn out to be binary compatible with 2.1.9
BTW, why did you include the extremely long ftobjs.c.orig file in your patch?
My bad. I must have used diff -ruN and this crept in.
Matthias
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
