Archive-Unzip-Burst
view release on metacpan or search on metacpan
keyword|||
leave_scope|||
lex_end|||
lex_start|||
linklist|||
listkids|||
list|||
load_module_nocontext|||vn
load_module||5.006000|v
localize|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHu|5.009002||p
mXPUSHi|5.009002||p
mXPUSHn|5.009002||p
mXPUSHp|5.009002||p
mXPUSHu|5.009002||p
magic_clear_all_env|||
unzip-6.0/INSTALL view on Meta::CPAN
then either "make generic2" or "make generic3" as instructed. If all
else fails, read the makefile itself; it contains numerous comments.
(One of these days we'll make a configure script that automates this
procedure better.)
VMS (OpenVMS):
On VMS, two build methods are provided: a command procedure, and
description files for MMS or MMK. Both methods must be run from
the main directory, not the [.VMS] subdirectory.
A simple build using the command procedure looks like this:
@ [.VMS]BUILD_UNZIP.COM
A simple build using MMS or MMK looks like this:
MMS /DESCRIP = [.VMS]DESCRIP.MMS ! Or, with MMK, ...
MMK /DESCRIP = [.VMS]DESCRIP.MMS
Various options for each build method are explained in comments in
the main builder file, either BUILD_UNZIP.COM or DESCRIP.MMS.
Here are some more complex build examples:
o Build with the large-file option enabled (non-VAX only):
unzip-6.0/macos/README.TXT view on Meta::CPAN
Mac filenames are changed to a most compatible filename.
Creator/Type: 'ZIP ' / 'ZIP '
- PKZIP/mac v2.03/210d. This is Shareware.
This Zip implementation for the Mac can be found on ASI's web site
(http://www.asizip.com/products/products.htm). The name of this
program is misleading, it is NOT a product from PKWARE. ASI's last
release version is v2.03, and they also offer a newer beta version
PKZIP/mac 210d. But even the Beta version is rather outdated (1995).
Only minimal Mac-info is stored (Creator/Type, Finder attributes).
The Zipfile format looks like incompatible to other platforms.
(More details about the compatibility issue can be found in
proginfo/3rdparty.bug!). Type: 'PKz1'
Mac filenames are restored without any change.
- Aladdin DropZip 1999, This is Shareware. Aladdin chose
the format of ZipIt. Therefore, it has the some drawbacks
like ZipIt.
Creator/Type: 'SITx' / 'ZIP '
- SmartZip 1.0 1999 - by Marco Bambini Vampire Software.
unzip-6.0/match.c view on Meta::CPAN
match(string, pattern, ignore_case, sepc);
returns TRUE if string matches pattern, FALSE otherwise. In the pattern:
`*' matches any sequence of characters (zero or more)
`?' matches any single character
[SET] matches any character in the specified set,
[!SET] or [^SET] matches any character not in the specified set.
A set is composed of characters or ranges; a range looks like ``character
hyphen character'' (as in 0-9 or A-Z). [0-9a-zA-Z_] is the minimal set of
characters allowed in the [..] pattern construct. Other characters are
allowed (i.e., 8-bit characters) if your system will support them.
To suppress the special syntactic significance of any of ``[]*?!^-\'', in-
side or outside a [..] construct, and match the character exactly, precede
it with a ``\'' (backslash).
Note that "*.*" and "*." are treated specially under MS-DOS if DOSWILD is
defined. See the DOSWILD section below for an explanation. Note also
unzip-6.0/proginfo/extrafld.txt view on Meta::CPAN
This field contains the information about which certificate in
the PKCS#7 store was used to sign the central directory structure.
When the Central Directory Encryption feature is enabled for a
ZIP file, this record will appear in the Archive Extra Data Record,
otherwise it will appear in the first central directory record,
along with the store. The data structure is the
same as the CID, except that SigSize will be 0, and there
will be no Sig member.
This field is also kept after the last central directory
record, as the signature data (ID 0x05054b50, it looks like
a central directory record of a different type). This
second copy of the data is the Signature Data member of the
record, and will have a SigSize that is non-zero, and will
have Sig data.
Note: all fields stored in Intel low-byte/high-byte order.
Value Size Description
----- ---- -----------
(CDID) 0x0016 2 bytes Tag for this "extra" block type
unzip-6.0/proginfo/fileinfo.cms view on Meta::CPAN
If you do not use periods as separators, there is no limit to how
much whitespace you can have before and after the filename, the
filetype, and filemode.
Opening a File without a File Mode Specified
If you omit the file mode or specify * for it, C/370 does one
of the following when you call fopen() or freopen():
* If you have specified a read mode, C/370 looks for the named file
on all the accessed readable disks, in order. If it does not find
the file, the fopen() or freopen() call fails.
* If you have specified any of the write modes, C/370 writes the file
on the first writable disk you have accessed. Specifying a write
mode on an fopen() or freopen() call that contains the filename of
an existing file destroys that file. If you do not have any
writable disks accessed, the call fails.
fopen() and freopen() parameters
unzip-6.0/proginfo/fileinfo.cms view on Meta::CPAN
try to write a short record, C/370 pads the record with nulls out
to LRECL.
At the completion of an fwrite(), the file position is at the start
of the next record. For new data, the block is flushed out to the
system as soon as it is full.
fldata() Behavior
When you call the fldata() function for an open CMS minidisk file,
it returns a data structure that looks like this:
struct __filedata {
unsigned int __recfmF : 1, /* fixed length records */
__recfmV : 1, /* variable length records */
__recfmU : 1, /* n/a */
__recfmS : 1, /* n/a */
__recfmBlk : 1, /* n/a */
__recfmASA : 1, /* text mode and ASA */
__recfmM : 1, /* n/a */
__dsorgPO : 1, /* n/a */
unzip-6.0/unix/Packaging/preinstall.in view on Meta::CPAN
echo " "
echo "REPORT ALL BUGS, PROBLEMS, AND ACCOLADES TO:"
echo " "
echo " Zip-Bugs@lists.wku.edu"
echo " "
echo "Checking architecture platform for .ARCH. ..."
arch=`uname -p`
if [ "arch_${arch}" != "arch_.ARCH." ]; then
echo " "
echo "This product MUST be installed on a Solaris .ARCH. platform."
echo "Your machine looks like it is a ${arch} platform."
echo "Please install the version for the .ARCH. architecture."
echo "Aborting the installation because of this. "
echo " "
returncode=1
else
echo " "
echo "This product works on .ARCH., which you happen to have!"
echo " "
returncode=0
fi
unzip-6.0/vms/INSTALL.VMS view on Meta::CPAN
VMS (OpenVMS):
On VMS, two build methods are provided: a command procedure, and
description files for MMS or MMK. Both methods must be run from
the main directory, not the [.VMS] subdirectory.
A simple build using the command procedure looks like this:
@ [.VMS]BUILD_UNZIP.COM
A simple build using MMS or MMK looks like this:
MMS /DESCRIP = [.VMS]DESCRIP.MMS ! Or, with MMK, ...
MMK /DESCRIP = [.VMS]DESCRIP.MMS
Various options for each build method are explained in comments in
the main builder file, either BUILD_UNZIP.COM or DESCRIP.MMS.
Here are some more complex build examples:
o Build with the large-file option enabled (non-VAX only):
unzip-6.0/vms/vms.c view on Meta::CPAN
* Segregated user query function from file re-open functions/code.
*
* There was no code in create_qio_output() to deal with an
* SS$_DUPFILENAME condition, leading to ugly run-time failures, and its
* requirements differ from those of the RMS (non-QIO) functions,
* create_default_output() and create_rms_output().
*
* Whether it makes sense to have a second layer of VMS-specific
* querying after the generic UnZip query in extract.c:
* extract_or_test_entrylist() is another question, but changing that
* looks more scary than just getting the VMS-specific stuff to work
* right (better?).
*/
/* "File exists" handler(s). Ask user about further action. */
/* RMS create new version. */
static int replace_rms_newversion(__GPRO)
{
int ierr;
struct NAM_STRUCT nam;
unzip-6.0/vms/vms.c view on Meta::CPAN
#define W(p) (*(unsigned short*)(p))
#define L(p) (*(unsigned long*)(p))
#define EQL_L(a, b) ( L(a) == L(b) )
#define EQL_W(a, b) ( W(a) == W(b) )
/*
* Function find_vms_attrs() scans the ZIP entry extra field, if any,
* and looks for VMS attribute records. Various date-time attributes
* are ignored if set_date_time is FALSE (typically for a directory).
*
* For a set of IZ records, a FAB and various XABs are created and
* chained together.
*
* For a PK record, the pka_atr[] attribute descriptor array is
* populated.
*
* The return value is a VAT_* value, according to the type of extra
* field attribute data found.
unzip-6.0/windll/windll.txt view on Meta::CPAN
Wiz_SingleEntryUnzip() returns a PKWARE compatible error code (0 if no
error or warning). For an explanation of the supported error codes see
the UnZip user documentation (the UnZip man page).
For examples of how the actual calls to the dll are set up in WiZ, look in
the files action.c and wizmain.c in the WiZ source directory. For a trival
example of how to load and call the dll, look in uzexampl.c and uzexampl.h.
For examples of how the actual loading and unloading of the dll's themselves
was done, look in wizmain.c in the WiZ source directory. Note that WiZ looks
specifically for a particular version number of the dll, and also expects to
find the company name to be Info-ZIP. This is to protect from getting
different versions of the dll loaded, with resulting unknown behavior.
Additional entry points:
const UzpVer * WINAPI UzpVersion(void);
where UzpVer is defined as:
unzip-6.0/windll/windll.txt view on Meta::CPAN
`?' matches any single character
[SET] matches any character in the specified set,
[!SET] or [^SET] matches any character not in the specified set.
In case the code was compiled with WILD_STOP_AT_DIR enabled, the pattern
wildcard functionality is modified as follows:
`*' matches any sequence of characters (zero or more) until the first
occurence of the separating character denoted by `sepc'
`**' matches any sequence of characters (zero or more)
A set is composed of characters or ranges; a range looks like ``character
hyphen character'' (as in 0-9 or A-Z). [0-9a-zA-Z_] is the minimal set of
characters allowed in the [..] pattern construct. Other characters are
allowed (i.e., 8-bit characters) if your system will support them.
To suppress the special syntactic significance of any of ``[]*?!^-\'', in-
side or outside a [..] construct, and match the character exactly, precede
it with a ``\'' (backslash).
The remaining functions are linked together. Their use would be as
follows (explanations for each function are shown further below):
( run in 0.577 second using v1.01-cache-2.11-cpan-64827b87656 )