package provided by Miles Nordin in PR 26774
rzip is a compression program, similar in functionality to gzip or
bzip2, but able to take advantage long distance redundencies in files,
which can sometimes allow rzip to produce much better compression
ratios than other programs.
Introduce HAVE_FILE_FLAGS if the system declares UF_SETTABLE and SF_SETTABLE
in addition to member 'st_flags' of struct stat. Use HAVE_FILE_FLAGS instead
of HAVE_STRUCT_STAT_ST_FLAGS.
This avoids confusion on UnixWare which has 'st_flags' but does _not_ support
file flags.
from previous include:
- include a pax2nbcompat script to ease importing from src HEAD
into pkgsrc.
* for copy mode, show more meaningful information on SIGINFO.
version of libnbcompat instead of requiring libnbcompat to be installed.
This simplifies testing of bootstrap packages without root privileges
on a system that has already been bootstrapped.
include:
- Make new() comply with the documentation and return undef on
a read() failure.
- Re-adds bin/ptar, which disappeared from this distribution after
0.22 (sorry about that).
- Fix a file renaming bug that forgot to carry over path info
- Fix a bug where adding dirs on win32 gave 'permission denied'
- Add extra tests explicilty for Archive::Tar::File
- Move completely from FileHandle to IO::File
- Quell some annoying warnings about binmode on unopened filehandles
- Add tests for binary files included in a tarball
- The chown() code somehow didn't make it into the 1.05 release
- Patch _get_handle() to treat all IO::File handles as binary.
This should make win32 users happy
- A method called 'contains_file' that will tell you if a certain file
is already in the archive.
- Add a global variable $CHOWN that controls whether Archive::Tar
should attempt to chown() files or not when it can.
- NULL-byte padding was done also on files that had no real content,
like symlinks, thus ending up with a number of bytes not dividable
by 512.
- Always do a readlink on the full path, never just the file
- Make Archive::Tar write proper headers when dealing with symlinks
For this $Archive::Tar::FOLLOW_SYMLINKS is introduced
Changes since 3.10.20:
* arj_arcv.c, arj_file.c, arj_proc.c, arj_user.c, arjtypes.c,
environ.c, externs.c, externs.h, makefile:
Merged with the remaining part of TCO fixes to make up for 3.10.21
* defines.h, encode.c, environ.c, environ.h, fmemcmp.asm, misc.c,
rearj.c: Resync with TCO to close any outstanding bugs
* arj.c: Rudimentary Borland code caused the filenames in argv[] to
be mishandled under Win32
* register.c: REGISTER might fail due to _fput_* changes
So you thought you had your files backed up onto that jaz cartridge -
until it came time to restore. Then you found out that you had bad
sectors and you've lost almost everything because gzip craps out 10%
of the way through your archive. The gzip Recovery Toolkit has a program
- gzrecover - that attempts to skip over bad data in a gzip archive and
to GNU tar that enables that program to skip over bad data and extract
whatever files might be there.
