On Feb 27, 2005, at 9:45 AM, Martin Costabel wrote:
This formulation comes from a time when there was no xfree86-4.0 and especially no xorg package yet. Right now we have no unique "freetype that is part of XFree86". We are forced to live with several different not really compatible freetype2 versions simultaneously, and this will remain so for a long time to come.
To recall the situation once more: We have [....]
Thanks a lot for your summary.
My personal option for a solution would be to
- first upgrade the current freetype2 package to 2.1.4. This is trivial to do. And to
- have an additional freetype219 package that installs everything (including all its library files) into %p/lib/freetype219.
Sounds good to me.
There remain unsolved problems which we will probably have to live with:
- Packages that don't care about freetype versions will get whatever is currently installed in /usr/X11R6, and they will build different debs for different X11s. Packages like qt3 should be encouraged to choose one of our versions.
- Often there will be two different freetype.6.dylibs loaded into memory at the same time, because X11's libfreetype will inevitably pop up in addition to ours.
This inevitability seems to be an issue for me. Specifically, in lilypond, I saw major breakage if I just linked with the default pango libraries because (it seemed) lilypond and pango were talking to different instances of freetype. I had to build a 219-dependent pango package. Is this the way to go forward?
Matthias
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
