With git master, fontconfig now loads all configuration files in /usr/share/fontconfig/conf.avail after loading the desired system configuration. This conflicts with the desired system configuration. For example, if the system has enabled 70-no-bitmaps.conf, 70-yes-bitmaps.conf is loaded later and overrides it.

This appears to be due to

    (void) FcConfigParseOnly (config, (const FcChar8 *)FC_TEMPLATEDIR, FcFalse);

in FcInitLoadOwnConfig. The intent seems to be to parse the files for their syntax and descriptions only, but it appears that the configurations are added to the selection rules anyway.

With fontconfig 2.12.6 on my system

    $ fc-list :scalable=false

returns no fonts because 70-no-bitmaps.conf is enabled.

With git master, and the same system configuration,

    $ ./fc-list/fc-list :scalable=false
    /usr/share/fonts/X11/75dpi/courR24-ISO8859-1.pcf.gz: Courier:style=Regular
    /usr/share/fonts/X11/75dpi/courR08-ISO8859-1.pcf.gz: Courier:style=Regular
    ...

FC_DEBUG=1024 shows that fontconfig is "scanning" conf.avail files instead of "loading".

If I delete the call to FcConfigParseOnly, then the "scanning" output disappears and the fc-list and fc-match results behave correctly.