No subject

point to the current font's fontconfig file, and pass this to the font provider
script. I think this is achieved by some magic in our existing font macros
which will take the name of the font-fontconfig file and write it into (say)
/tmp/fake-fonts.conf and create a macro called %__font_provides_opts which
contains this name.

When fontconfig.prov is called, the name of our faked fontconfig file will be
passed on the command line, and we use that to set up the FONTCONFIG_FILE
environment variable.

My sticking point is not knowing exactly when everything gets evaluated during
building the font package, so I don't know which macro should magically create
this temporary fontconfig root file (and, presumably, cleanly dispose of it).

-- 
You are receiving this mail because:
You are on the CC list for the bug.