Permalink
Commits on Oct 18, 2017
  1. 4.0.2

    zkat committed Oct 18, 2017
  2. deps: bump devDeps

    zkat committed Oct 18, 2017
  3. deps: bump minipass and minizlib

    zkat committed Oct 18, 2017
    This should get tar working on node@9
Commits on Aug 21, 2017
  1. v4.0.1

    isaacs committed Aug 21, 2017
Commits on Aug 18, 2017
  1. v4.0.0

    isaacs committed Aug 18, 2017
  2. unpack: raise error if cwd is missing or not a dir

    isaacs committed Aug 18, 2017
    Fix #134
    
    Note: this is a breaking change, because a command that previously would
    not throw an error now might.
Commits on Aug 17, 2017
  1. v3.2.0

    isaacs committed Aug 17, 2017
  2. Add uid/gid options to extract and unpack

    isaacs committed Aug 17, 2017
    Enables forcibly setting the ownership of all extracted items,
    regardless of the uid/gid of the process or the value in the archive.
    
    This also avoids calling chown on files and directories if they are
    already going to be owned by the proper uid/gid (that is, if the
    specified uid/gid matches the process uid and gid).
    
    Note that it does _not_ set the ownership of pre-existing folders that
    are already in place when the extract is performed.  It only guarantees
    that files and directories created by the unpack will have their
    ownership set as specified.  Thus it provides a reliable gaurantee of
    file ownership only if extracting into a previously empty directory.
    
    Fix #133
  3. add chownr as a dep

    isaacs committed Aug 17, 2017
  4. v3.1.15

    isaacs committed Aug 17, 2017
Commits on Aug 16, 2017
  1. v3.1.14

    isaacs committed Aug 16, 2017
  2. Include size in PAX extended header

    isaacs committed Aug 16, 2017
    bsdtar does not properly handle the base-256 encoded xstar size value.
    
    Fixes #131
  3. v3.1.13

    isaacs committed Aug 16, 2017
  4. Do not attempt to call getgid/getuid if not a function

    isaacs committed Aug 16, 2017
    Just no-op the whole 'preserveOwner' junk in that case.
Commits on Aug 15, 2017
  1. v3.1.12

    isaacs committed Aug 15, 2017
  2. v3.1.11

    isaacs committed Aug 15, 2017
  3. unpack: go ahead and emit 'end'

    isaacs committed Aug 15, 2017
    No sense trying to be correct.  The semantics are too confusing.
  4. v3.1.10

    isaacs committed Aug 15, 2017
  5. unpack: pretend harder to be a strict writable stream

    isaacs committed Aug 15, 2017
    Even run tests with end-of-stream.
    
    Presumably, this will fix #132.
  6. require node 4.5 as minimum

    Justin Helmer committed with isaacs Jun 27, 2017
  7. Do not munge file list arrays

    isaacs committed Aug 15, 2017
    Fix #120
Commits on Aug 2, 2017
  1. v3.1.9

    isaacs committed Aug 2, 2017
  2. Unpack: do not emit 'end'

    isaacs committed Aug 2, 2017
    Since the Unpack class is a writable stream, but not a readable stream,
    it doesn't make sense for it to emit an 'end' event.  What we're really
    after is a 'close' event which means 'done writing all the things'.
    
    However, since the Parse class already used 'end' in many cases, and
    this event name was being consumed (and is, in general, safe if one is
    merely parsing, and not doing asynchronous unpacking as well), it's
    being left in place.
    
    Many stream utilities call the stream 'done' at the first occurrence of
    any end-of-stream style thing: finish, end, done, close, etc.
Commits on Aug 1, 2017
  1. v3.1.8

    isaacs committed Aug 1, 2017
  2. queue fs.chown and fs.utimes so that they happen prior to close

    isaacs committed Aug 1, 2017
    This makes some benchmarks slightly slower, but prevents issues where a
    chown or utimes is not happening until after the next file has started
    being written.  That can be a problem, because the subsequent file in an
    archive may in fact be trying to overwrite the prior file, creating a
    race condition where the resulting mode/mtime is non-deterministic.
Commits on Jul 26, 2017