The question is whether this could be used as an opportunity to scrap Fink's freetype2 packages.
For packages that on 10.2 Depend on freetype2, this could be actually be a benefit, because they wouldn't have to be changed between 10.2-gcc3.3 and 10.3, provided the new xfree86 packages and their virtual or system-* counterparts would Provide freetype2. If the freetype2 packages stay, then every other package that uses freetype2 has to be patched, as Ben R. has been doing recently, so that it actually does not use Fink's freetype2, but the one from X11.
Let me explain this at the example of the scribus package. If used with XF-4.2, it needs Fink's freetype2, because it uses some functions not present in the older freetype2 from xf-4.2. If used with XF-4.3, it could be built and run with or without Fink's freetype2 packages. Right now, this would mean two different package descriptions for 10.2-gcc3.3 and for 10.3, because Ben R's patch that makes sure only one freetype2 dylib is used (the one from X11), will only work with XF-4.3, but not with XF-4.2.
It seems more reasonable to me to modify the xfree86-4.3.0 and system-xfree86-43 packages so that they Provide and Replace freetype2 and also Conflict with freetype2, rather than patch every package that depends on freetype2. This could actually be done even now in 10.2-gcc3.3, and it seems to me the only possible solution that does not require changing package descriptions between 10.2-gcc3.3 and 10.3.
-- Martin
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
