GitLab

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

For objects which has been changed the object type to FcTypeRange.

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

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

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

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

Patch from Kurt Kartaltepe

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

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

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

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.