Daniel Macks wrote: []
Testing, however, finds that fink does the Right Thing here. Objection withdrawn. So why do you *ever* do '-x xfontconfig' in your *Script?
I think there is quite a bit of, let's say, "legacy code" (AKA old cruft) in these font packages. I can only speak for the msttcorefonts and applesystemfonts packages, because I looked at them before copying them over to 10.3 (with some modifications). They were needed for scribus and were working, so I adapted them to 10.3, although I understood there was an opinion (shared by their maintainer) that they shouldn't be necessary on Panther any more.
I took out the parts that were certainly not needed on Panther, like the dlcompat dependencies and the whole /etc/X11/XftConfig business that is coming from Xft1 and is totally useless for Xft2, that is for xfree86-4.3.0. This could also be removed from the gimp-*fonts packages.
OTOH, there were things I didn't touch, like the "-x xfontconfig" and the "`%p/bin/xfontpath basedir`". I don't know why they were there in the original packages, the extra security and flexibility they could possibly provide seems bogus indeed.
-- Martin
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
