We've long had xft2-dev and fontconfig2-dev keep their headers and libraries buried in subdirs so that they do not mask system (x11) supplied versions of those same packages. Maintainers must explicitly set some flag(s) to make them visible. And often experiment and hack to make sure they are consisently used in preference to x11's in those cases. For the past year or so, we've worked hard to use these intentionally whenever possible to avoid breakage every time apple or xquartz or whoever updates system files. And we keep finding problems where the maintainers try to do so, but get the flag-orders wrong and wind up getting x11's anyway.
Is it time to unbury these libraries? Doing so would mean much less magic and hacking needed, since they will "always" be visible. The drawback is that there are probably a few packages that use x11 directly will suddenly start seeing the fink libs. Anything that uses gnome or other GUI stacks was probably long ago fixed to use fink's explicitly, or else has always been broken anyway due to mixing and this might even get them consistent again. We did this a while ago with freetype and had no problems that I recall. The unburied package would still have the buried locations accessible as well for those packages that still use the (no-longer-needed) flags to point to them. Any objections? dan -- Daniel Macks dma...@netspace.org ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
