archive-zip 0.6.0 → 0.7.0

data/HACKING

@@ -1,105 +0,0 @@
-= Guide to Hacking Archive::Zip
-
-== Licensing
-
-Contributed code must be licensed under the same license as this project.  See
-the included LICENSE file for details.  Special consideration MAY be made in
-some cases, but such cases will be rare.
-
-
-== Dependencies
-
-=== Runtime
-
-* Ruby 1.8.6 or greater
-* io-like 0.3.0 or greater
-
-
-=== Build
-
-* rubygems 1.8.8 or greater
-* rake 0.9.2 or greater
-* rdoc 3.9.2 or greater
-* mspec 1.5.17 or greater
-
-
-=== Install
-
-* rubygems 0.9.0 or greater
-
-
-== Versioning Policy
-
-Version numbers will be in <em>x.y.z</em> format, where <em>x</em>, <em>y</em>,
-and <em>z</em> are integers starting from 0.  The version increment rules are
-as follows:
-
-<b>x</b>:: Planned releases which implement significant changes and/or break API
-           compatibility.  An exception is to be made for the transition from
-           the <em>0.y.z</em> series to the <em>1.y.z</em> series since the
-           <em>0.y.z</em> series is expected to be unstable throughout
-           development.  When incremented, <em>y</em> and <em>z</em> are reset
-           to 0.
-<b>y</b>:: Planned releases which incorporate numerous bug fixes and/or new
-           features which do not break backward compatibility.  When
-           incremented, <em>z</em> is reset to 0.
-<b>z</b>:: Generally, unplanned releases which incorporate a single fix for a
-           critical defect.
-
-This is the {Rational Versioning Policy}[http://www.rubygems.org/read/chapter/7]
-as outlined in the {RubyGems User Guide}[http://www.rubygems.org/read/book/1].
-
-
-== Support Policy
-
-Due to limitations in resources (time/money/manpower), this project will focus
-primarily upon the development line of the current release at any given time.
-Fixes and new features should be applied first to that development line and then
-backported to earlier releases if necessary and feasible.  Long term maintenance
-of previous releases is not planned.  Users are generally expected to upgrade to
-the latest release in order to receive updates unless an explicit declaration of
-support for a previous release is made.
-
-
-== Coding Style
-
-The following points are not necessarily set in stone but should rather be used
-as a good guideline.  Consistency is the goal of coding style, and changes will
-be more easily accepted if they are consistent with the rest of the code.
-
-<b>File Encoding</b>::     UTF-8
-<b>Indentation</b>::       Two spaces; no tabs
-<b>Comments</b>::          Document classes, attributes, methods, and code
-<b>Boolean Operators</b>:: Use <tt>&&</tt> and <tt>||</tt> for boolean tests;
-                           avoid <tt>and</tt> and <tt>or</tt>
-<b>Method Calls</b>::      Use <tt>a_method(arg, arg, etc)</tt>; <b>not</b>
-                           <tt>a_method( arg, arg, etc )</tt>,
-                           <tt>a_method arg, arg, etc</tt>, or any other
-                           variation
-<b>Blocks</b>::            <tt>do end</tt> for multi-line blocks and
-                           <tt>{ }</tt> for single-line blocks
-<b>Line length</b>::       Limit lines to a maximum of 80 characters
-<b>General</b>::           Try to follow the flow and style of the rest of the
-                           code
-
-
-== Contributing Code
-
-Making a contribution is pretty simple.  Fork the project on Github
-(http://github.com/javanthropus/archive-zip), make your changes, and submit a
-pull request.  Requests that meet the following criteria will be the most
-readily accepted:
-
-1. Each pull request should target an individual issue and should introduce
-   relatively few commits.
-2. Individual commits need to be small, easily digestible units.
-3. Good descriptions of the changes introduced should be included in each commit
-   message.
-4. Interdependencies on existing pull requests need to be noted in the pull
-   request.
-5. New test cases are a major plus.
-6. Documentation for new classes, methods, etc. is also a win.
-7. The coding style of the project should be respected.
-
-In other words, the less work necessary to bring your changes into the project,
-the faster you can expect them to be pulled.

data/LEGAL

@@ -1,8 +0,0 @@
-= Other Legalities
-
-== Files Licensed Differently
-
-The following file(s) are provided under a license or licenses separate from
-this project.
-
-  None at present

data/README

@@ -1,151 +0,0 @@
-= Archive::Zip - ZIP Archival Made Easy
-
-The Archive::Zip library intends to provide a simple, yet complete and
-Ruby-esque, interface to working with ZIP archives.
-
-Basic archive creation and extraction can be handled using only a few methods.
-More complex operations involving the manipulation of existing archives in place
-(adding, removing, and modifying entries) are also possible with a little more
-work.  Even adding advanced features such as new compression codecs are
-supported with a moderate amount of effort.
-
-
-== License
-
-Copyright © 2010 Jeremy Bopp <jeremy at bopp dot net>
-
-Licensed under the same terms as Ruby -- See the included LICENSE file for
-details
-
-
-== Installation/Removal
-
-Download the GEM file and install it with:
-  % sudo gem install archive-zip-VERSION.gem
-
-or directly with:
-  % sudo gem install archive-zip
-
-Removal is the same in either case:
-  % sudo gem uninstall archive-zip
-
-
-== Example
-More examples can be found in the +examples+ directory of the source
-distribution.
-
-Create a few archives:
-  gem 'archive-zip'  # Use require_gem for rubygems versions older than 0.9.0.
-  require 'archive/zip'
-
-  # Add a_directory and its contents to example1.zip.
-  Archive::Zip.archive('example1.zip', 'a_directory')
-
-  # Add the contents of a_directory to example2.zip.
-  Archive::Zip.archive('example2.zip', 'a_directory/.')
-
-  # Add a_file and a_directory and its contents to example3.zip.
-  Archive::Zip.archive('example3.zip', ['a_directory', 'a_file'])
-
-  # Add only the files and symlinks contained in a_directory under the path
-  # a/b/c/a_directory in example4.zip.
-  Archive::Zip.archive(
-    'example4.zip',
-    'a_directory',
-    :directories => false,
-    :path_prefix => 'a/b/c'
-  )
-
-  # Add the contents of a_directory to example5.zip and encrypt Ruby source
-  # files.
-  require 'archive/zip/codec/null_encryption'
-  require 'archive/zip/codec/traditional_encryption'
-  Archive::Zip.archive(
-    'example5.zip',
-    'a_directory/.',
-    :encryption_codec => lambda do |entry|
-      if entry.file? and entry.zip_path =~ /\.rb$/ then
-        Archive::Zip::Codec::TraditionalEncryption
-      else
-        Archive::Zip::Codec::NullEncryption
-      end
-    end,
-    :password => 'seakrit'
-  )
-
-  # Create a new archive which will be written to a pipe.
-  # Assume $stdout is the write end a pipe.
-  # (ruby example.rb | cat >example.zip)
-  Archive::Zip.open($stdout, :w) do |z|
-    z.archive('a_directory')
-  end
-
-Now extract those archives:
-  gem 'archive-zip'  # Use require_gem for rubygems versions older than 0.9.0.
-  require 'archive/zip'
-
-  # Extract example1.zip to a_destination.
-  Archive::Zip.extract('example1.zip', 'a_destination')
-
-  # Extract example2.zip to a_destination, skipping directory entries.
-  Archive::Zip.extract(
-    'example2.zip',
-    'a_destination',
-    :directories => false
-  )
-
-  # Extract example3.zip to a_destination, skipping symlinks.
-  Archive::Zip.extract(
-    'example3.zip',
-    'a_destination',
-    :symlinks => false
-  )
-
-  # Extract example4.zip to a_destination, skipping entries for which files
-  # already exist but are newer or for which files do not exist at all.
-  Archive::Zip.extract(
-    'example4.zip',
-    'a_destination',
-    :create => false,
-    :overwrite => :older
-  )
-
-  # Extract example5.zip to a_destination, decrypting the contents.
-  Archive::Zip.extract('example5.zip', 'a_destination', :password => 'seakrit')
-
-
-== Features
-
-1.  100% native Ruby.  (Well, almost... depends on zlib.)
-2.  Archive creation and extraction is supported with only a few lines of code.
-3.  Archives can be updated "in place" or dumped out to other files or pipes.
-4.  Files, symlinks, and directories are supported within archives.
-5.  Unix permission/mode bits are supported.
-6.  Unix user and group ownerships are supported.
-7.  Unix last accessed and last modified times are supported.
-8.  Entry extension (AKA extra field) implementations can be added on the fly.
-9.  Unknown entry extension types are preserved during archive processing.
-10. The Deflate and Store compression codecs are supported out of the box.
-11. More compression codecs can be added on the fly.
-12. Traditional (weak) encryption is supported out of the box.
-
-
-== Known Bugs/Limitations
-
-1.  More testcases are needed.
-2.  All file entries are archived and extracted in binary mode.  No attempt is
-    made to normalize text files to the line ending convention of any target
-    system.
-3.  Hard links and device files are not currently supported within archives.
-4.  Reading archives from non-seekable IO, such as pipes and sockets, is not
-    supported.
-5.  MSDOS permission attributes are not supported.
-6.  Strong encryption is not supported.
-7.  Zip64 is not supported.
-8.  Digital signatures are not supported.
-
-
-== Contributing
-
-Contributions for bug fixes, documentation, extensions, tests, etc. are
-encouraged.  Please read the file HACKING for details.

data/TODO

@@ -1,5 +0,0 @@
-= Future work items (in no particular order):
-
-* Add test cases for all classes.
-* Add support for using non-seekable IO objects as archive sources.
-* Add support for 0x5855 and 0x7855 extra fields.

data/default.mspec

@@ -1,8 +0,0 @@
-# encoding: UTF-8
-class MSpecScript
-  # An ordered list of the directories containing specs to run
-  set :files, ['spec']
-
-  # The default implementation to run the specs.
-  set :target, 'ruby'
-end

data/spec_helper.rb

@@ -1,49 +0,0 @@
-# encoding: UTF-8
-# Add the lib directory for this module to the search path.
-$: << File.join(File.dirname(__FILE__), 'lib')
-
-unless ENV['MSPEC_RUNNER']
-  begin
-    require 'mspec/version'
-    require 'mspec/helpers'
-    require 'mspec/guards'
-    require 'mspec/runner/shared'
-    require 'mspec/matchers/complain'
-
-    # Code to setup HOME directory correctly on Windows
-    # This duplicates Ruby 1.9 semantics for defining HOME
-    platform_is :windows do
-      if ENV['HOME']
-        ENV['HOME'] = ENV['HOME'].tr '\\', '/'
-      elsif ENV['HOMEDIR'] && ENV['HOMEDRIVE']
-        ENV['HOME'] = File.join(ENV['HOMEDRIVE'], ENV['HOMEDIR'])
-      elsif ENV['HOMEDIR']
-        ENV['HOME'] = ENV['HOMEDIR']
-      elsif ENV['HOMEDRIVE']
-        ENV['HOME'] = ENV['HOMEDRIVE']
-      elsif ENV['USERPROFILE']
-        ENV['HOME'] = ENV['USERPROFILE']
-      else
-        puts "No suitable HOME environment found. This means that all of"
-        puts "HOME, HOMEDIR, HOMEDRIVE, and USERPROFILE are not set"
-        exit 1
-      end
-    end
-
-    TOLERANCE = 0.00003 unless Object.const_defined?(:TOLERANCE)
-  rescue LoadError
-    puts "Please install the MSpec gem to run the specs."
-    exit 1
-  end
-end
-
-minimum_version = "1.5.17"
-unless MSpec::VERSION >= minimum_version
-  puts "Please install MSpec version >= #{minimum_version} to run the specs"
-  exit 1
-end
-
-# Set a flag when encodings are supported.
-MSpec.enable_feature :encoding if Object.const_defined?(:Encoding)
-
-$VERBOSE = nil unless ENV['OUTPUT_WARNINGS']