Update LICENSE
Upstream changes:
0.26 (2018/06/09)
Implemented refactoring due warnings from Perl::Critic.
0.25 (2018/06/04)
Implemented refactoring due warnings from Perl::Critic.
Merge pull request #3 from manwar/suggest-code-tidy
0.24 (2018/06/02)
Added a LICENSE file (GNU GPL v3).
Removed MYMETA files (see https://rt.cpan.org/Ticket/Display.html?id=108171).
Improved Kwalitee by adding information to Makefile.PL
Fixed tests under OpenBSD
Added some code to check for OpenBSD tar, which is not quite compatible to the command line options passed by this module.
Also made the method is_gnu() more robust, testing the return code and properly handling STDOUT and STDERR when trying "tar --version".
Dependencies added are those already available on standard perl (Config and IPC::Open3).
Added a README.md for better formatting in Github project page.
Small refactorings and code formating with perltidy.
Problems found with existing distfile for eagle:
distfiles/bicom101.zip
distfiles/szip-2.1nb3/szip-2.1.tar.gz
distfiles/xmill-0.9.1.tar.gz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
-------------------
0.22 (2015/03/08)
(ms) Added tar_gnu_write_options option suggested by Csaba Major with
tests and docs.
0.21 (2014/10/16)
(ms) [rt.cpan.org 87536] Setting default umask to get predictable test
results regardless of local umask settings.
0.20 (2014/09/29)
(ms) Ignore errors on chown/chgrp when files from different owners/groups
are copied into a tarball, accept the limitation that they'll be
owned by the script user unless we're running as superuser.
0.19 (2014/02/16)
(ms) RsrchBoy added support for bzip2-compressed tarfiles.
Archive::Tar::Wrapper is an API wrapper around the 'tar' command line
utility. It never stores anything in memory, but works on temporary
directory structures on disk instead. It provides a mapping between the
logical paths in the tarball and the 'real' files in the temporary
directory on disk.
It differs from Archive::Tar in two ways:
- Archive::Tar::Wrapper doesn't hold anything in memory. Everything is
stored on disk.
- Archive::Tar::Wrapper is 100% compliant with the platform's tar
utility, because it uses it internally.
