Tuesday, April 30, 2013

Beranda » , » Exclude Files from a Zip Archive Mac OS X

Exclude Files from a Zip Archive Mac OS X

The easiest way to exclude many specific files or a group of matched files from a zip archive is by skipping the easy zipping utility built into Mac OS X’s friendly UI and turn over to the command line, where the powerful zip command resides.

This is useful for a million and one reasons, but the primary motivation for this post pertains to the .DS_Store files which get bundled along with zip archives created on a Mac, only to clutter up another machine that unzips the file, whether it’s on another Mac, Windows PC, or linux. That happens with both the friendly zip tool and the command line zip utility by default, and it’s because the zipping tools default behavior is to including hidden files whether they are shown or not. That’s not necessarily a bad thing and in many cases it would be considered useful, but if you don’t want them, or any other file for that matter, showing up in your archives, then read on.

Excluding Files from a Zip Archive

The basics of file exclusion when creating a zip archive are centered around the -x flag, which is used to exclude files from the archive that match a specific name or pattern. At it’s most basic, it will look like this:
zip archive.zip files -x "ExcludeMe"
Meaning you could exclude a single file, say it’s named “Nothanks.jpg”
zip archive.zip images/ -x "Nothanks.jpg"
Let’s cover a few specific examples where this is useful.

Exclude .DS_Store Files from Zip Archives

This will prevent the typically invisible Mac metadata .DS_Store files from being included in a zip archive, which are bundled in by default:
zip -r archivename.zip archivedirectory -x "*.DS_Store"
If the directory includes subdirectories however, you’ll want to use another variation of that command to exclude the the ds_store files from subdirectories as well:
zip -r archive.zip directory -x "*/\.DS_Store"
Note: not all shells require the quotations for this command to work properly, but in the bash shell (the default for OS X) you will need to use the quotes for excluding with wildcards and patterns.

Exclude Specific File Types from a Zip Archive

With wildcards, you can also exclude all files of a certain type by focusing on the extension. For example, this command will zip an entire directory, minus any .jpg files:
zip -r archive.zip directory -x "*.jpg"
That could be modified for any specific file extension or pattern matched in a file name.

Exclude the .git or .svn Directory from a Zip Archive

Zip a directory, minus .git and it’s contents:
zip -r zipdir.zip directorytozip -x "*.git*"
Zip a folder, without including the .svn directory:
zip -r zipped.zip directory -x "*.svn*"
Exclude All Hidden Files from a Zip Archive
Since patterns and wildcards can be used, you could also exclude any or all invisible files and folders that are made so by being prefixed with a period, whether it’s a directory like .svn or an individual file like .bash_profile or .htaccess.
zip -r archivename.zip directorytozip -x "*.*"
Or to exclude all invisible files from all subdirectories:
zip -r archive.zip directory -x "*/\.*"
Cheers to a commenter on the Macworld Forums for the precise syntax on excluding those files from subdirectories as well.

Ultimately, this is just another reason for power users to jump to the Terminal for creating archives. With powerful features like wildcard support, exclusion, and optional password protection of zips, it’s just more full-featured, and since it’s all included on the Mac anyway you won’t need to download another app to support the advanced features.

And yes, technically if you were determined to stay in the UI you could use Finder and Spotlight search operators to narrow down a folders contents in OS X before creating an archive, or just Select All and manually Command+Click each file to not include, but that is really not efficient for large archiving operations. Thus, the terminal wins out for ease, and despite being centered around the command line, it’s really not complicated once you learn the basics.

Note: If this tutorial worked for you (and it should work), please leave a comment below. Thanks.