which included commits to RCS files with non-trunk default branches. git-svn-id: svn://10.65.10.50/trunk@5403 c028cbd2-c16b-5b4b-a496-9718f37d4682
		
			
				
	
	
		
			137 lines
		
	
	
		
			6.6 KiB
		
	
	
	
		
			Plaintext
		
	
	
		
			Executable File
		
	
	
	
	
			
		
		
	
	
			137 lines
		
	
	
		
			6.6 KiB
		
	
	
	
		
			Plaintext
		
	
	
		
			Executable File
		
	
	
	
	
| Copyright (C) 1990-1996 Mark Adler, Richard B. Wales, Jean-loup Gailly,
 | |
| Onno van der Linden, Kai Uwe Rommel, Igor Mandrichenko and John Bush.
 | |
| Permission is granted to any individual or institution to use, copy, or
 | |
| redistribute this software so long as all of the original files are included,
 | |
| that it is not sold for profit, and that this copyright notice is retained.
 | |
| 
 | |
| 
 | |
| Zip 2.1 is a compression and file packaging utility.  It is compatible with
 | |
| PKZIP 2.04g (Phil Katz ZIP) for MSDOS systems.  There is a companion to zip
 | |
| called unzip (of course) which you should be able to find the same place
 | |
| you got zip. See the file 'Where' for details on ftp sites and mail
 | |
| servers.
 | |
| 
 | |
| This version of zip has been ported to a wide array of Unix and other
 | |
| mainframes, minis, and micros including VMS, OS/2, Minix, MSDOS, Windows NT,
 | |
| Atari, Amiga and VM/CMS. Although highly compatible with PKware's PKZIP and
 | |
| PKUNZIP utilities of MSDOS fame, our primary objective has been one of
 | |
| portability and other-than-MSDOS functionality.  Features not found in the
 | |
| PKWare version include creation of zip files in a pipe or on a device, VMS
 | |
| and OS/2 extended file attributes, conversion from Unix to MSDOS text file
 | |
| format; and, of course, the ability to run on most of your favorite operating
 | |
| systems.  And it's free.
 | |
| 
 | |
| See the file 'history' for a detailed list of all changes.
 | |
| 
 | |
| This version does not support multi-volume archives as in pkzip 2.04g.
 | |
| This may be provided in a future version if time permits.
 | |
| 
 | |
| Please read the file install.doc for information on how to compile and
 | |
| install zip, zipsplit and zipnote.  Please read the file zip.doc for
 | |
| information on how to use them.  The file "contents" is a complete
 | |
| list of the files you should have in this distribution.  Also, if you
 | |
| are using MSDOS, you should read the note on file formats at the end
 | |
| of the contents file.
 | |
| 
 | |
| This version supports encryption, but the encryption code is distributed
 | |
| separately because of the US export regulations. See the file 'Where'
 | |
| for access to the encryption code. Decryption can be made with unzip 5.0p1
 | |
| or later, or with zipcloak (which is provided in the encryption supplement).
 | |
| 
 | |
| All bug reports or patches should go to zip-bugs@wkuvx1.wku.edu, and
 | |
| suggestions for new features can be sent to info-zip@wkuvx1.wku.edu
 | |
| (although we don't promise to use all suggestions).  Patches should be
 | |
| sent as context diffs only (diff -c).
 | |
| 
 | |
| If you're considering a port, please check in with zip-bugs FIRST,
 | |
| since the code is constantly being updated behind the scenes.  We'll
 | |
| arrange to give you access to the latest source.
 | |
| 
 | |
| If you'd like to keep up to date with our Zip (and companion UnZip utility)
 | |
| development, join the ranks of BETA testers, add your own thoughts and con-
 | |
| tributions, etc., send a two-line mail message containing the commands HELP
 | |
| and LIST (on separate lines in the body of the message, not on the subject
 | |
| line) to mxserver@wkuvx1.wku.edu.  You'll receive two messages listing the
 | |
| various Info-ZIP mailing-list formats which are available (and also various
 | |
| unrelated lists) and instructions on how to subscribe to one or more of them
 | |
| (courtesy of Hunter Goatley).
 | |
| 
 | |
| Frequently asked questions on zip and unzip:
 | |
| 
 | |
| Q. When unzipping I get an error message about "compression method 8".
 | |
| 
 | |
| A. Please get the latest version of unzip. See the file Where for details.
 | |
| 
 | |
| 
 | |
| Q. I can't extract this zip file that I just downloaded. I get
 | |
|    "zipfile is part of multi-disk archive" or some other message.
 | |
| 
 | |
| A. Please make sure that you made the transfer in binary mode. Check
 | |
|    in particular that your copy has exactly the same size as the original.
 | |
|    
 | |
| 
 | |
| Q. When running unzip, I get a message about "End-of-central-directory
 | |
|    signature not found".
 | |
| 
 | |
| A. This usually means that your zip archive is damaged, or that you
 | |
|    have an uncompressed file with the same name in the same directory.
 | |
|    In the first case, it makes more sense to contact the person you
 | |
|    obtained the zip file from rather than the Info-Zip software
 | |
|    developers, and to make sure that your copy is strictly identical to
 | |
|    the original.  In the second case, use "unzip zipfile.zip" instead
 | |
|    of "unzip zipfile", to let unzip know which file is the zip archive
 | |
|    you want to extract.
 | |
| 
 | |
| 
 | |
| Q. Why doesn't zip do <something> just like PKZIP does?
 | |
| 
 | |
| A. Zip is not a PKZIP clone and is not intended to be one.  In some
 | |
|    cases we feel PKZIP does not do the right thing (e.g., not
 | |
|    including pathnames by default); in some cases the operating system
 | |
|    itself is responsible (e.g., under Unix it is the shell which
 | |
|    expands wildcards, not zip).  Info-ZIP's and PKWARE's zipfiles
 | |
|    are interchangeable, not the programs.
 | |
| 
 | |
|    For example, if you are used to the following PKZIP command:
 | |
|                pkzip -rP foo *.c
 | |
|    you must use instead on Unix:
 | |
|                zip -r foo . -i \*.c
 | |
|    (PKZIP does not allow  recursion in directories other than the
 | |
|    current one. zip does, this is why the syntax is different.)
 | |
| 
 | |
| 
 | |
| Q. Can I distribute zip and unzip sources and/or executables?
 | |
| 
 | |
| A. You may redistribute the latest official distributions without any
 | |
|    modification, without even asking us for permission. You can charge
 | |
|    for the cost of the media (CDROM, diskettes, etc...) and a small copying
 | |
|    fee.  If you want to distribute modified versions please contact us at
 | |
|    zip-bugs@wkuvx1.wku.edu first. You must not distribute beta versions.
 | |
|    The latest official distributions are always on ftp.uu.net in directory
 | |
|    /pub/archiving/zip and subdirectories.
 | |
| 
 | |
| 
 | |
| Q. Can I use the executables of zip and unzip to distribute my software?
 | |
| 
 | |
| A. Yes, so long as it is made clear in the product documentation that
 | |
|    zip or unzip are not being sold, that the source code is freely
 | |
|    available, and that there are no extra or hidden charges resulting
 | |
|    from its use by or inclusion with the commercial product. Here is
 | |
|    an example of a suitable notice:
 | |
| 
 | |
|      NOTE:  <Product> is packaged on this CD using Info-ZIP's compression
 | |
|      utility.  The installation program uses UnZip to read zip files from
 | |
|      the CD.  Info-ZIP's software (Zip, UnZip and related utilities) is
 | |
|      free and can be obtained as source code or executables from various
 | |
|      anonymous-ftp sites, including ftp.uu.net:/pub/archiving/zip/*.
 | |
| 
 | |
| 
 | |
| Q. Can I use the source code of zip and unzip in my commercial application?
 | |
| 
 | |
| A. Yes, so long as you include in your product an acknowledgment and an
 | |
|    offer of the original compression sources for free or for a small
 | |
|    copying fee, and make clear that there are no extra or hidden charges
 | |
|    resulting from the use of the compression code by your product. In other
 | |
|    words, you are allowed to sell only your own work, not ours. If you have
 | |
|    special requirements contact us at zip-bugs@wkuvx1.wku.edu.
 |