1. 04 Apr, 2019 1 commit
  2. 03 Apr, 2019 5 commits
    • Akira TAGOH's avatar
      Don't share fonts and cache dir for testing · 34791c32
      Akira TAGOH authored
      There seems a race condition on CI. so create an unique directory to avoid colision.
    • Akira TAGOH's avatar
      Add salt attribute to dir and remap-dir elements · 2e8ce635
      Akira TAGOH authored
      'salt' attribute affects a cache filename to generate different name from directory name.
      This is useful when sharing caches with host on sandbox and/or give a filename differently:
          <dir salt="randomdata">/usr/share/fonts</dir>
          <remap-dir as-path="/usr/share/fonts" salt="salt for /usr/share/fonts on host">/run/host/fonts</remap-dir>
      Applications can read caches as-is for fonts on /run/host/fonts where is mounted from host.
      and write a cache for their own fonts on /usr/share/fonts with different name.
    • Akira TAGOH's avatar
      Update testcase · 916cf6ca
      Akira TAGOH authored
    • Keith Packard's avatar
      Replace UUID file mechanism with per-directory 'map' attribute [v2] · c4324f54
      Keith Packard authored
      The UUID files would be placed in each font directory to provide the
      unique cache name, independent of path, for that directory. The UUID
      files are undesireable for a couple of reasons:
       1) They must be placed in the font directories to be useful. This
          requires modifying the font directories themselves, introducing
          potential visible timestamp changes when running multiple
          applications, and makes the cache processing inconsistent between
          applications with permission to write to the font directories and
          applications without such permission.
       2) The UUID contents were generated randomly, which makes the font
          cache not reproducible across multiple runs.
      One proposed fix for 2) is to make the UUID dependent on the font
      directory path, but once we do that, we can simply use the font
      directory path itself as the key as the original MD5-based font cache
      naming mechanism did.
      The goal of the UUID file mechanism was to fix startup time of
      flatpaks; as the font path names inside the flatpak did not match the
      font path names in the base system, the font cache would need to be
      reconstructed the first time the flatpak was launched.
      The new mechanism for doing this is to allow each '<dir>' element in
      the configuration include a 'map' attribute. When looking for a cache
      file for a particular directory, if the directory name starts with the
      contents of the <dir> element, that portion of the name will be
      replaced with the value of the 'map' attribute.
      Outside of the flatpak, nothing need change -- fontconfig will build
      cache files using real directory names.
      Inside the flatpak, the custom fonts.conf file will now include
      mappings such as this:
      	<dir map="/usr/share/fonts">/run/host/fonts</dir>
      When scanning the directory /run/host/fonts/ttf, fontconfig will
      use the name /usr/share/fonts/ttf as the source for building the cache
      file name.
      The existing FC_FILE replacement code used for the UUID-based
      implementation continues to correctly adapt font path names seen by
      	Leave FcDirCacheCreateUUID stub around to avoid removing
      	public API function.
      	Document 'map' attribute of <dir> element in
      Suggested-by: Akira TAGOH's avatarAkira TAGOH <akira@tagoh.org>
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
    • Keith Packard's avatar
      Remove UUID-related tests · 4cde12bf
      Keith Packard authored
      Remove test-hash
      Remove UUID tests from run-test.sh
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
  3. 23 Mar, 2019 1 commit
  4. 22 Mar, 2019 1 commit
  5. 25 Oct, 2018 1 commit
  6. 29 Aug, 2018 1 commit
  7. 11 Jun, 2018 1 commit
  8. 25 May, 2018 1 commit
  9. 13 May, 2018 1 commit
  10. 28 Mar, 2018 1 commit
  11. 18 Dec, 2017 2 commits
  12. 05 Dec, 2017 1 commit
  13. 20 Nov, 2017 3 commits
  14. 21 Mar, 2017 1 commit
  15. 24 Nov, 2015 1 commit
  16. 17 Jan, 2014 1 commit
  17. 31 Dec, 2012 1 commit
  18. 28 Aug, 2006 1 commit
    • Keith Packard's avatar
      During test run, remove cache directory to avoid stale cache usage. · 7a03bbdc
      Keith Packard authored
      As file timestamps have only one second granularity, an old cache
      file could easily be used when a test took less than 1 second to run.
      Just remove the cache directory and its contents before each test is run.
      Also, remove mention of the old cache file from the test config file.
  19. 04 Aug, 2006 1 commit
  20. 27 Oct, 2003 1 commit
  21. 15 Jun, 2003 1 commit
  22. 01 Mar, 2003 1 commit