Re: prebuilding 32-bit caches on a 64-bit system
"Keith Packard" <[email protected]>
| Newsgroups | gmane.comp.fonts.fontconfig |
|---|---|
| Message-ID | <[email protected]> |
Lawrence D'Oliveiro <[email protected]> writes: > Isn’t there /usr/libexec for executables that are in some sense > “internal” to a package? (E.g. Git puts its subcommands > into /usr/libexec/git-core, at least on my Debian system.) Oh, that's almost certainly distro-dependent. Debian sticks the git programs in /usr/lib/git-core. So, either /usr/libexec/fontconfig or /usr/lib/fontconfig would be a fine plan, and of course distro packagers would dtrt. For automake, we would use pkglibexecdir and that should work for everyone -- it'll be /usr/lib/fontconfig on debian and /usr/libexec/fontconfig on redhat. Do we want to stick the fc-cache variants in a fc-cache.d subdirectory so that the script can safely use a simple filename glob pattern? -- -keith _______________________________________________ Fontconfig mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/fontconfig
signature.asc
(application/pgp-signature, 832 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAlpVP1IACgkQ2yIaaQAA ABEtjRAAnwQlMM+JP2f22Xuob8+M+cZJarQLu2FfoQJ/UEDHH9cW64H78bqT9gRW 7UfMYqxgzZsl3vpuKLAsIgKpFBqno5qIBTBeuco/tV1oqVdC1Sc8crUehmylUfHz AkShyo5EqnsDEixWXL7uzBBLqIhifmat9VGkVHVeXWRvOz68Rt0hnDoyU7udf/mr CHkUGa5qDkyvqFACdyykT5rUksWj3BWcHqoWh0CcrZ+cVMnis8lBKfdNXlI5fdFQ mSkBsheFpIJTu6rb7n8ss0HXpYo3ZZNRj1PCRqs+Z1c28JDKOWECHMbFXUY6bhf9 3Lnx9+X5IpgfyVBY/Qm51GwkYfqDProfIT0yuBGnyY8yIpyDOp3a0ynCPEoXvF1W qFpOWB3dw+xeEPDp0jAZQBal+hWQk0q7ksgwAhdOp+DwyCWjpfCRmgbMZqyrg2Mf wXw9tcvWCXrdmZ1Ia39VLECNaUjXrBLICf7soNhTnC1JVDedjzmtKL2BTY3ijn+s 3yPcmVI7Mgs9kPhhWM42NYQIUorBqpTtz6GvCO84BXYA0YXC0AJWtG8roHOBU00D lu4+bLuzQt4bkMTKjBPPTAmqubOQWe+2/dtg48hVAn71X3EtPilzD2clKinMKvas 7VpCPyzPVaRO8wLlCh87Yet+mrUwGsRVhoGtSmvSdDohSCKc338= =Ib78 -----END PGP SIGNATURE-----