Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-05-23 | tar: turns out --sparse is also known as -S. | Elliott Hughes | |
Found trying to build the aosp_cf_x86_phone-userdebug target. The good news is that the targets that I knew were using tar with sparse files all pass now. | |||
2019-05-20 | Less incomplete tar help text. | Rob Landley | |
2019-05-19 | Fix tar sparse extract with extension blocks. | Rob Landley | |
2019-05-19 | Fix tar --sparse generation of extension block. | Rob Landley | |
2019-05-19 | Add pointless trailing --sparse entry for exact binary compartibility. | Rob Landley | |
There's no possible use for this, but debian's tar produces it, so... | |||
2019-05-19 | Add --sparse file creation support to tar. | Rob Landley | |
And fix tar cv to produce output to stderr when archive going to stdout. | |||
2019-05-14 | Checked in a debugging printf. Oops. | Rob Landley | |
2019-05-14 | Typo caused a segfault. (Oops.) | Rob Landley | |
2019-05-13 | Fix a couple error paths that don't continue archive create/extract properly. | Rob Landley | |
2019-05-11 | Teach tar to extract type 'S' sparse file headers. | Rob Landley | |
2019-05-01 | tar: use same tools for decompression as for compression. | Elliott Hughes | |
This is what GNU tar does, so Android's build system jail allows bzip2, gzip, and xz, but not bzcat, zcat, and xzcat. Why the function? Because auto-detection works by setting toyflags, so we need to make sure we test the flags late, so it's either two copies of this or a function. | |||
2019-04-21 | Promote tar. | Rob Landley | |
There's probably more to do, but it seems usable at this point. |