Those elements takes effects immediately during parsing config files so makes them conditional to ignore on scanning.

Using Requires is peferable way.

https://bugs.freedesktop.org/show_bug.cgi?id=104622

Alexander Larsson authored Jan 12, 2018 and Akira TAGOH committed Jan 14, 2018

We were comparing the passed in key with the ready-to-insert key
rather than the key in the hashtable, so if you ever had a hash
conflicts we'll never insert the new item.

https://bugs.freedesktop.org/show_bug.cgi?id=101889

and drop the dependency of itstool.
To get this working, need to patch out to fix a crash:
http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=a0cab23332a254e3500cac2a3a984472d02180e5

Tom Anderson authored Jan 03, 2018 and Behdad Esfahbod committed Jan 04, 2018

Fontconfig symbols were hardcoded to be either hidden or exported.  This patch
adds configurable symbol visibility.  This is useful for projects that want to
do in-tree fontconfig builds and not export any symbols, otherwise they would
conflict with the system library's symbols

Chromium is a project that does in-tree fontconfig builds, and the workaround
currently used is "#define visibility(x) // nothing" [1] and building with
"-fvisibility=hidden".
[1] https://cs.chromium.org/chromium/src/third_party/fontconfig/BUILD.gn?rcl=ce146f1f300988c960e1eecf8a61b238d6fd7f7f&l=62

No idea why I didn't add these as double to begin with.

Ie. flip the merge order.

This is the last piece of the puzzle for variable-font support in
fontconfig.  This takes care of automatically setting the variation
settings when user requests a weight / width / size that has variation
in the matched font.

Ouch!

Alexander Larsson authored Dec 18, 2017 and Akira TAGOH committed Dec 19, 2017

When we replace a bucket in the hashtable we have to update the
next pointer too, or we lose all the other elements that hashed to
this key.

Not proper fix necessarily. But fixes this crash:
https://bugs.freedesktop.org/show_bug.cgi?id=101889#c81