1. 29 Aug, 2018 2 commits
  2. 28 Aug, 2018 1 commit
  3. 21 Aug, 2018 1 commit
  4. 01 Aug, 2018 1 commit
    • Akira TAGOH's avatar
      Fix the build issue with gperf · a1efb5ea
      Akira TAGOH authored
      GPerf seems not allowing the empty lines though, current recipes are supposed to drop them.
      but seems not working on some env.
      So taking the proper way to do that instead of incompatible things against platforms.
      a1efb5ea
  5. 26 Jul, 2018 1 commit
  6. 25 Jul, 2018 4 commits
  7. 19 Jul, 2018 14 commits
  8. 16 Jul, 2018 2 commits
    • Tom Anderson's avatar
      Return canonicalized paths from FcConfigRealFilename · d1f48f11
      Tom Anderson authored
      FcConfigRealFilename() follows symlinks, but the link may be relative to the
      directory containing the link.  For example, on my system, I have this file:
      
      /etc/fonts/conf.d/99-language-selector-zh.conf ->
          ../conf.avail/99-language-selector-zh.conf
      
      Since /etc/fonts/conf.d is probably not in PATH, open()ing the file would fail.
      This change makes FcConfigRealFilename() return the canonicalized filename
      instead.  So for the example above, it would return:
      
      /etc/fonts/conf.avail/99-language-selector-zh.conf
      
      This was causing bad font rendering in Chromium [1] after the regression I
      introduced in 7ad010e8.
      
      [1] https://bugs.chromium.org/p/chromium/issues/detail?id=857511
      d1f48f11
    • Behdad Esfahbod's avatar
      Use FT_HAS_COLOR · 48e9e5f4
      Behdad Esfahbod authored
      48e9e5f4
  9. 10 Jul, 2018 1 commit
  10. 13 Jun, 2018 1 commit
  11. 11 Jun, 2018 2 commits
  12. 08 Jun, 2018 1 commit
  13. 25 May, 2018 7 commits
  14. 16 May, 2018 1 commit
    • Chris Lamb's avatar
      Ensure cache checksums are deterministic · f098adac
      Chris Lamb authored
      Whilst working on the Reproducible Builds[0] effort, we noticed that
      fontconfig generates unreproducible cache files.
      
      This is due to fc-cache uses the modification timestamps of each
      directory in the "checksum" and "checksum_nano" members of the _FcCache
      struct. This is so that it can identify which cache files are valid
      and/or require regeneration.
      
      This patch changes the behaviour of the checksum calculations to prefer
      the value of the SOURCE_DATE_EPOCH[1] environment variable over the
      directory's own mtime. This variable can then be exported by build
      systems to ensure reproducible output.
      
      If SOURCE_DATE_EPOCH is not set or is newer than the mtime of the
      directory, the existing behaviour is unchanged.
      
      This work was sponsored by Tails[2].
      
       [0] https://reproducible-builds.org/
       [1] https://reproducible-builds.org/specs/source-date-epoch/
       [2] https://tails.boum.org/
      f098adac
  15. 13 May, 2018 1 commit