Skip to content
Snippets Groups Projects
  1. Jun 08, 2021
  2. Jun 07, 2021
  3. Jun 04, 2021
  4. Jun 02, 2021
  5. Jun 01, 2021
  6. May 27, 2021
  7. May 26, 2021
  8. May 25, 2021
  9. May 20, 2021
  10. May 18, 2021
  11. May 17, 2021
  12. May 12, 2021
  13. May 11, 2021
  14. May 07, 2021
  15. Apr 30, 2021
    • Simon McVittie's avatar
    • Simon McVittie's avatar
      Update changelog · 1fa5d59f
      Simon McVittie authored
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      1fa5d59f
    • Ludovico de Nittis's avatar
      Merge branch 'wip/smcv/mtree' into 'master' · 20e57546
      Ludovico de Nittis authored
      pressure-vessel: Use a mtree(5) manifest to set up the runtime
      
      See merge request !295
      20e57546
    • Simon McVittie's avatar
      runtime: Add support for creating runtime from a mtree(5) · 799b7931
      Simon McVittie authored
      
      At the moment we deploy the runtime from a giant tarball to avoid Steam
      downloader limitations, but that leads to a noticeable delay the first
      time we launch a game after a new runtime version has been downloaded.
      
      Now that the Steam download mechanism can deal better with larger
      numbers of smaller files, we're considering returning to the original
      design where the runtime depot contains unpacked files. However, the
      Steam download mechanism doesn't preserve permissions, modification
      times, or filenames that differ only by case, and has not always
      preserved empty directories, so we need a way to deal with all of
      those things.
      
      By reading a manifest written in a subset of the BSD mtree(5) format,
      we can create directories and symlinks, and set permissions modification
      times on regular files. As a bonus, it's actually slightly faster to
      duplicate a runtime with hard-links (--copy-runtime mode) by reading the
      manifest than by reading the actual directory tree, because the manifest
      is more likely to be contiguous on disk.
      
      In principle the mtree(5) manifest could also be used to validate that
      the runtime content has not become corrupted by checking files against
      their sha256sums. This isn't implemented here (and it would have to be
      done only on demand rather than routinely, because it would be slow),
      but the parser does at least read the sha256.
      
      In the tests, we now need to remove the mtree manifest when copying
      and editing a runtime. When we edit a runtime in-place, it no longer
      conforms to the manifest, so this can't necesarily be expected to work.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      799b7931
Loading