Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_pkg / refs/heads/upstream/0.9.x / . / tests / testdata
tree: 2f1ac07217876ba89366a64bdab11788a0f0e6a0 [path history] [tgz]
  1. utf8/
  2. outer_BUILD ⇨ ../BUILD
  3. a.ar
  4. a_ab.ar
  5. a_b.ar
  6. a_b_ab.ar
  7. ab.ar
  8. b.ar
  9. config
  10. deb_preinst
  11. deb_triggers
  12. empty.ar
  13. executable.sh
  14. file_with_a_ridiculously_long_name_consectetur_adipiscing_elit_fusce_laoreet_lorem_neque_sed_pharetra_erat.txt
  15. hello.txt
  16. loremipsum.txt
  17. README.md
  18. tar_test.tar
  19. tar_test.tar.bz2
  20. tar_test.tar.gz
  21. tar_test.tar.xz
  22. templates
  23. test_tar_package_dir_file.txt
  24. utf8_linux.tar
  25. utf8_linux.zip
  26. utf8_mac.tar
  27. utf8_mac.zip
  28. utf8_win.tar
  29. utf8_win.zip
tests/testdata/README.md

This folder contains test data.

The utf8 folder contains a set of files whose names are not ASCII or ISO-8859-1. They may be used for testing the ability to handle files using non ASCII file names. Along with those we have 4 samples of what native tar and zip utilities do with these file names:

  • utf8_linux.tar: From linux: tar cf utf8_linux.tar utf8
  • utf8_linux.zip From linux: zip -r utf8_linux.zip utf8
  • utf8_mac.tar: From macos: tar cf utf8_linux.tar utf8
  • utf8_mac.zip From macos: zip -r utf8_linux.zip utf8
  • utf8_win.tar: From window: tar cf utf8_win.tar utf8
  • utf8_win.zip From window: 7z a -r utf8_win.zip utf8

The samples are are intended to be used as input data for tests of capabilities that read data (such as unpacking and filtering a tar file). Code must be able to read tar and zip files produced on a different OS and interpret file names correctly. For now we can study the differences by platform.