Matthias/All,
On 01/02/2005, at 6:14 PM, Matthias Neeracher wrote:
For my upcoming lilypond 2.5.x package, I need a pango that a) is newer than 1.4 and b) does not link against the system freetype2.
I have therefore a) upgraded the pango packages to 1.6 (I believe the latest version that does not require upgrading other gnome components) and b) added -ftdev variants that link against freetype2-dev instead of the system freetype2. The regular variants and the -ftdev variants are designed to coexist on the same system, and the latter should never appear in an include/link path unless explicitly requested.
[SNIP]
I am definitely not here to object, but I think we need to examine the whole freetype/fontconfig/XFree86/Xorg issue. I'm in the process of testing out some builds of GNOME 2.9.90, which contains Pango 1.8.0 - it too requires a more recent version of both freetype and fontconfig than is provided by XFree86 or Apple X11. Is there not a better way to do this? Why are we so afraid of packaging these libraries as complete (%n, %n-shlibs, %n-dev) solutions into fink? It'd certainly solve a few problems with the newer releases of GNOME (and not having to rely on the user having the latest X.org or XFree86 release). I am pretty close to putting a Depends on xorg for Pango 1.8.0 at this point and being done with it, but I'd prefer not to...
Thoughts?
-Tony
------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
