Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
6
contributors
Commits on Oct 8, 2015
Commits on Mar 27, 2017
-
-
-
-
-
-
-
rewrite header as class, organize field management
This removes a lot of tar.fieldOffs[tar.fields[fieldName]] business. There's an internal Field class which knows its beginning and end, and can read a value from a buffer, or write it back to a buffer.
-
Commits on Mar 30, 2017
Commits on Mar 31, 2017
-
-
-
-
-
Remove 'realtime' and 'security' PAX fields
They were 'reserved for a future specification' 3 decades ago and never used.
-
Commits on Apr 3, 2017
Commits on Apr 4, 2017
-
-
-
-
-
-
don't force blockLen > size if even multiple of 512
Confuses bsdtar into thinking the file is over
-
parallel api sugar for lib/extract.js
These really need to be rethought, though. Here's the plan that's coming: For create helper methods, the options object should take a list of files to add to the tarball. If a file is specified, then write out to the file. Otherwise, return the stream, which can be piped as the user sees fit. If no cb is provided, return a Promise. Actually, just return a Promise no matter what, maybe? The goal is to mimic the command line. So, to replicate `tar czf my-tarball.tgz files and folders`, you'd do: tar.c( { gzip: <true|gzip options>, file: 'my-tarball.tgz', glob: <true|glob options> }, ['some', 'files', 'and', 'folders'] ).then(_ => { .. tarball has been created .. }) To replicate `tar cz files and folders > my-tarball.tgz`, you'd do: tar.c( { gzip: <true|gzip options>, glob: <true|glob options> }, ['some', 'files', 'and', 'folders'] ).pipe(fs.createWriteStream('my-tarball.tgz') To replicate `tar xf my-tarball.tgz` you'd do: tar.x( { file: 'my-tarball.tgz' } ).then(_=> { .. tarball has been dumped in cwd .. }) To replicate `cat my-tarball.tgz | tar x -C some-dir --strip=1`: fs.createReadStream('my-tarball.tgz').pipe( tar.x({ strip: 1, C: 'some-dir' // alias for cwd:'some-dir', also ok }) ) To replicate `tar tf my-tarball.tgz`, do this: tar.t({ file: 'my-tarball.tgz' }) .on('entry', entry => { .. do whatever with it .. }) To replicate `cat my-tarball.tgz | tar t` do: fs.createReadStream('my-tarball.tgz') .pipe(tar.t()) .on('entry', entry => { .. do whatever with it .. }) To do anything synchronous, add `sync: true` to the options. -
-
Commits on Apr 5, 2017
-
-
-
-
-
While only 2 files are covered right now, getting any shortage of test coverage reported as a failure is a great practice.
-
Not much to test, since it's just 2 map objects, but whatever.
-
header: support setting the fieldset type
Also: validate 'type' field, and split the prefix/path properly when the prefix size is 0 (because basic fieldset).
Commits on Apr 6, 2017
Commits on Apr 7, 2017
-
Move byte counting into read-entry
Also, move 'turn a number into a date' into consistent places, so we store epoch seconds, rather than a javascript Date.toString() value.
There are no files selected for viewing