Around 15 o'clock on May 21, Jon Leech wrote:
> Sounds good - but in the meantime, it might be good to remove it > from the build, so that it doesn't prevent installs in nonstandard > locations from completing. If fontconfig is truly not related to X, > should it even be in the X tree? Fontconfig is not dependent on X, but X is dependent on fontconfig, and XFree86 has a practice of shipping non-standard packages along with the window system to avoid adding new dependencies to existing systems. I'm putting the finishing touches on making fontconfig buildable outside of the X tree by using autoconf, that build process places the configuration files in reasonable places as it has definitions for the standard system configuration directory. > I tried overriding FontconfigDir in site.def, but that wasn't > sufficient, and the install still fails trying to write into font > directories it locates under /usr/share. Fontconfig wants to build caches for available fonts to avoid having every user build private caches when the first fontconfig-using application is invoked. The build process now skips that step when DESTDIR is set. What problem are you trying to avoid by skipping this step? Keith Packard XFree86 Core Team HP Cambridge Research Lab _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
