Remove executable bit.

Update README.md

- Minor refactoring
- Rubify Java-ish code
- Fix issue with `::Zip` reference
- Add test to ensure integrity

Fix Recursive zipping example

update master

Conflicts:
	README.md
	samples/example_recursive.rb

This reverts commit 8c13dfc.

Add configs of rubocop gem and fix some rubocop warnings

Instead of inheriting the permissions from the tmp directory, new files should
have permissions that reflect the defaults on the system taking umask into
account.

It seems that (unix) permissions of 666 - umask are as close to a standard as
anything [1] and that 'touch' uses this. On Windows it seems sensible to just
use 644 directly [2].

[1] http://unix.stackexchange.com/a/102080
[2] http://ruby-doc.org/core-1.9.3/File.html

Do something more expected with new file permissions.

Accept StringIO in Zip.open_buffer

…non existant zips

[#241]Added error for empty (zero bit) zip file. Added tests for empty and …

Use duck typing with IO methods.

Fix exception due to calling empty? on nil.

When support for ZipCrypto was added, an internal StringIO buffer was
added to Deflater, in order to fix a decryption bug. While this worked,
it caused unlimited memory growth when compressing large files. The
proper fix is to writer the encryption header in init_next_entry instead
of finalize_current_entry, so the headers are written before any
encrypted data. Because of this fix we can remove the buffering in
Deflater, which keeps memory usage low and allows to stream compressed
data while it is written.

This should fix issue #233.

Fix high memory usage due to Deflater buffering

…tests

See http://stackoverflow.com/questions/34351144/minitest-assert-output-incorrect-check-for-stderr
about this

Fix TypeError: can't dup NilClass from EntrySet#dup

Add correct test for `Zip.warn_invalid_date` attribute

Fix accidental unlink (#185) without using ObjectSpace (#252)

Replacing 'puts' with 'write' as 'puts' was adding extra lines in files,
damaging them. Ref : #260

Fix typo file name in samples/example_filesystem.rb

Fix in example_recursive

…on was buggy on windows systems)

To make copy-pasting work :D

Small change to "Modify docx file with rubyzip"

Add changelog entries for RubyZip 1.2.0

...instead of comparing against in-ruby subtraction math.

This test fails because in *NIX when the umask is 0027, files are created with 0640 permissions. The current implementation of Zip::File.create_file_permissions does a simple subtraction of 0666 - 0027 == 0637

Before this change:
  1) Failure:
FilePermissionsTest#test_umask_027 [/Users/marcoswk/workspace/rubyzip/test/file_permissions_test.rb:52]:
Expected: 33184
  Actual: 33183

After this change:
  1) Failure:
FilePermissionsTest#test_umask_027 [/Users/marcoswk/workspace/rubyzip/test/file_permissions_test.rb:52]:
--- expected
+++ actual
@@ -1,2 +1,2 @@
 # encoding: US-ASCII
-"100640"
+"100637"

…in file

example_recursive.rb lost some special characters ( for example 0x1a at file end ) , it should related to io stream implementation . Use internal zip add method instead of File.read could avoid this lose . 

An issue is posted at #296

After running the tests there was a file left in the project directory,
'empty.zip', which was simply 'touch'ed to use as a null file. Switch to create
this as one of the generated test files so it's cleaned up automatically.

Also, use 'null.zip' as the name as there is already an 'empty.zip' generated
that is a zip file, but empty.

This fixes #294 in what I hope is a more sensible way than trying to mess with
umasks, etc, directly.

Temporary files were being created with 0600 permissions and then being set to
different permissions, based on umask, etc, afterwards. I don't know what the
rationale for this was, but there were errors in the umask calculations when
moving from the temporary file to the intended end result.

Now we don't differentiate between Windows and Linux in the library code for
this, we don't need separate tests.

Rubies available are detailed here: http://rubies.travis-ci.org/