view release on metacpan or  search on metacpan

CHANGES  view on Meta::CPAN

1.70 15/11/2010
- Add ptargrep utility courtesy of Grant McLean

1.68 17/08/2010
- Apply a patch from Colin Newell that checks whether long files can be created or
  not in 02_methods.t. Hopefully resolves RT #57312 and RT #56163

1.66 26/07/2010
- Applied a patch from Alexandr Ciornii [RT#59699] to Makefile.PL which produces better META.yml
- Apply a patch from Alexandr Ciornii to ptar [RT#59700]:

    Adds option -C to allow archives created with ptar to be uploaded to
    PAUSE in case of Windows or world +w permissions on unix.

1.64 09/07/2010
- Removed the PERL_CORE specific chdir from all the tests
- Apply a patch from David Muir Sharnoff RT #58916,
  "skip files via a callback and limit memory use when skipping files"
- Apply a patch from Daphne Pfister RT #59150
  "Assumes all references filename are IO::Handle's instead of trying to stringify."

1.62 28/06/2010
- Apply part of patch from https://bugzilla.redhat.com/attachment.cgi?id=426194
  reported by Martin Cermak in RT #58636 relating to a Redhat ticket
  https://bugzilla.redhat.com/show_bug.cgi?id=606813

1.60 23/04/2010
- Apply patch from Darrell K. [RT #54850] that makes write() and create_archive() close only handles
  they opened.

    When you pass a filehandle to Archive::Tar::write() or create_archive(),
    it closes the filehandle after writing to it. I think it makes more
    sense not to close a handle that A::T didn't open, since the application
    may need to write additional data to it. (Consider sockets, package
    files containing encapsulated tar archives, etc.)

    Example:

    $ perl -e 'use Archive::Tar; open(PKG, ">mypkg") or die "open: $!"; my
    $tar = Archive::Tar->new; $tar->add_data("foo.txt","hello");
    $tar->write(\*PKG); print PKG "more data" or die "print: $!";'
    print: Bad file descriptor at -e line 1.

- Fool the installer into replacing our scripts that were installed by core with versiononly set.

1.58 17/02/2010
- Apply a patch from toddr@null.net that addreses RT #54714

  Subject: $@ not cleaned up after eval

  This section of code seems to be trying to use future functionality
  not yet present in IO::Zlib (tell). I was chasing another bug and getting very confused
  by this population of $@. Could I request you cleanup $@ if you expect and/or don't care
  about failure from this eval?

1.56 03/02/2010
- Apply a patch from Mark Swayne that addresses RT #50471;

  Archive::Tar generates file headers with space padded numbers for size,
  mtime and checksum. This format is incompatible with some versions of
  the busybox implementation of tar (I am using 1.13.2), which requires 0
  padded numbers (despite comments in the source that say otherwise).

  I've included a patch that adds a control flag that enables zero padded
  numbers in the header. It passes all tests with ActiveState Perl 5.8.8
  on WinXP.

1.54 10/09/2009
- Apply a patch from Niko Tyni (ntyni@debian.org) that resolves RT #48879;

    As seen in [rt.cpan.org #48879], although the recommended way of
    retrieving the last error is to use an instance method ($tar->error),
    the returned value is effectively global: an error in one Archive::Tar
    instance changes the error string of another instance.

    This change separates the error strings from each other while keeping
    the (deprecated) global value of $Archive::Tar::error pointing to the
    last error regardless of its instance.

    We also support calling error() as a class method (Archive::Tar->error).
    In this case it returns the global value, which matches the old behaviour.

1.52 13/06/2009:
- Apply documentation patch to describe IBM APAR issue IZ50240; AIX tar
  does not always end a Tar archive with a 0x00 null block, which can
  cause warnings from Archive::Tar.
  This is a documentation patch only, and users of 1.50 need not upgrade.

1.50 12/06/2009:
- Apply patch in #46450: Support for --no-same-permissions style behavior
  This facilitates leaving the +x bit, while still applying your umask on
  the extracted file.

1.48 20/04/2009:
- Address #44680 (Improve error reporting on short corrupted archives)
  Archives of less than 512 bytes would not have a clear error string set
- Requires at least IO::Compres::* 2.015, to address: #43609: Memory
  problem with A::T. Turns out 2.012 was leaking memory.

1.46 05/03/2009:
- Address: bug #43513: [PATCH] Accept wrong checksums from SunOS and HP-UX tar
  like GNU tar does. See here for details:
  http://www.gnu.org/software/tar/manual/tar.html#SEC139
- make COMPRESS_BZIP and COMPRESS_GZIP constants actually work and fix their
  documentation

1.44 19/01/2009:
- Address #41798: Nonempty $\ when writing a Tar file produces a
  corrupt Tar file
- Textual fix to Makefile.PL diagnostics

1.42 13/12/2008:
- Address #40426: Archive Tar to support direct Archive::Tar::File adds
  It is now possible to add Archive::Tar::File objects via $tar->add_files
- Address #40016 (Archive::Tar assumes $> won't change): CAN_CHOWN is now a
  dynamic check upon extraction. This allows scripts to drop privileges when
  desired
- Address take 2 of #39933: [PATCH] handle ../ directory name on VMS
  John M. sent in a better way to do directory name translation.

1.40 13/10/2008: