Comments on: Ruby: Unzipping a file using rubyzip

By: Aninda

Aninda — Sun, 20 Jun 2010 18:05:17 +0000

Hi Mark,
Thanks for your example. I was wondering how you would deal with the scenario that you have a zip file within a zip file?

By: Michael Larkin

Michael Larkin — Thu, 09 Jul 2009 03:55:15 +0000

Thanks! This was a great example.

I added a next unless f.file? to skip directories (they’re created automatically by the mkdir_p call) as well as filtering out the junk files like .DS_STORE, Thumbs.db, __MAC_OSX and such.

By: grosser

grosser — Wed, 04 Feb 2009 06:59:53 +0000

here comes the reverse example:
packing a folder to a zip file

http://pragmatig.wordpress.com/2009/02/04/compressing-a-folder-to-a-zip-archive-with-ruby/

By: John

John — Mon, 06 Oct 2008 17:00:38 +0000

Mark, another problem is when you want to make a ZIP on, say, a Windows system that doesn’t have Cygwin. In other words, no native ZIP. Without a native ZIP (that understand -r) you also can’t do rake package (unless things have changed recently). Here’s a hack at making a ZIP from Ruby. I would love to have a more robust version of this.

# Drop-in for zip for those who don’t have one on their systems.
# For this, you will first need to
# gem install rubyzip
#

require ‘rubygems’
require ‘zip/zip’

recursive = false
if ARGV[0] == ‘-r’
recursive = true
ARGV.shift
end

archive = ARGV.shift
ARGV.each do |arg|
files = recursive ? Dir[ arg + '/**/*.*' ] : [arg]
files.each do |f|
Zip::ZipFile.open(archive, Zip::ZipFile::CREATE) do |z|
begin
z.remove(f)
rescue
end
entry = f.dup
# blech
if (entry[0..1] == ‘./’)
entry = entry[2..-1]
end
z.add(entry, f)
puts ” adding #{f}”
end
end
end

By: Greg

Greg — Thu, 02 Oct 2008 22:36:23 +0000

http://blog.thoughtfolder.com/code/e.rb

unzips any file on linux

By: Scott

Scott — Thu, 02 Oct 2008 05:24:53 +0000

“calling a binary from ruby isn’t exactly kosher”. Sure it is, just make sure to properly check stdout and stderr as needed to make sure everything went as planned.

By: Lisa Seelye

Lisa Seelye — Wed, 01 Oct 2008 20:36:09 +0000

You’re better off just piping to your local unzip binary. The rubyzip library isn’t very well made (even though it seems like the only thing we have) and the native unzip binary is just so powerful that it makes sense to harness it, even though calling a binary from ruby isn’t exactly kosher.