mirror of https://github.com/bazelbuild/rules_pkg
2247f5d88d
Duplicate path entries are made possible within tar archives as discussed in feature request #849. This includes an interaction with create parents, where the only logical scenario which would require inference of a parent directory is when one does not already exist. This is because allowance of duplicates is only useful when explicit paths are declared. RELNOTES: Duplicate path entries supported within tar archives |
||
|---|---|---|
| .. | ||
| utf8 | ||
| README.md | ||
| a.ar | ||
| a_ab.ar | ||
| a_b.ar | ||
| a_b_ab.ar | ||
| ab.ar | ||
| b.ar | ||
| config | ||
| deb_preinst | ||
| deb_triggers | ||
| duplicate_entries.tar | ||
| empty.ar | ||
| executable.sh | ||
| file_with_a_ridiculously_long_name_consectetur_adipiscing_elit_fusce_laoreet_lorem_neque_sed_pharetra_erat.txt | ||
| hello.txt | ||
| loremipsum.txt | ||
| outer_BUILD | ||
| tar_test.tar | ||
| tar_test.tar.bz2 | ||
| tar_test.tar.gz | ||
| tar_test.tar.xz | ||
| templates | ||
| test_tar_package_dir_file.txt | ||
| utf8_linux.tar | ||
| utf8_linux.zip | ||
| utf8_mac.tar | ||
| utf8_mac.zip | ||
| utf8_win.tar | ||
| utf8_win.zip | ||
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.