On 27 Feb 2005, at 18:45, Martin Costabel wrote:
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.
This would allow new packages to choose between 2.1.4 and 2.1.9, every package would find at least one compatible freetype2 version, and there would be neither build time nor runtime conflicts. All freetype2-{dev,shlibs} and freetype219-{dev,shlibs} packages can be installed at the same time.
Sounds perfect _ but are you sure you want 2.1.4 ?
I see only the following pkgs in 10.3/unstable that depend on freetype2 :
mozilla peacock ghex paragui pong gnome-pim autotrace scribus xdvik transcode mlterm
If you know that one or more of them cannot use anything higher than 2.1.4,
and cannot be updated, that's it. But else, isn't it worth to run a quick test ?
I observe that several of those pkgs have not been updated since long _ so the
fact that I'm using 2.1.7 w/o trouble since long doesn't prove anything about them...
Just recompiling them on an old panther machine to be sure .
Best,
JF
------------------------------------------------------- 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
