How to tell gzip to keep original file?

Question

How to tell gzip to keep original file?

I would like to compress a text file using gzip command line tool while keeping the original file. By default running the following command

gzip file.txt

results in modifying this file and renaming it file.txt.gz. instead of this behavior I would like to have this new compressed file in addition to the existing one file.txt. For now I am using the following command to do that

gzip -c file.txt > file.txt.gz

It works but I am wondering why there is no easier solution to do such a common task ? Maybe I missed the option doing that ?

Asked By: Manuel Selva

||

Source

Answer 1

From the documentation it seems that there is no option to create a copy of the file.

You can define a shell function

gzipkeep() {
    if [ -f "$1" ] ; then
        gzip -c -- "$1" > "$1.gz"
    fi
}

and then

gzipkeep file.txt

Answered By: Matteo

Answer 2

For GNU gzip 1.6 or above, FreeBSD and derivatives or recent versions of NetBSD, see don_cristi’s answer.

With any version, you can use shell redirections as in:

gzip < file.txt > file.txt.gz

When not given any argument, gzip reads its standard input, compresses it and writes the compressed version to its standard output. As a bonus, when using shell redirections, you don’t have to worry about files called "--help" or "-" (that latter one still being a problem for gzip -c --).

Another benefit over gzip -c file.txt > file.txt.gz is that if file.txt can’t be opened, the command will fail without creating an empty file.txt.gz (or overwriting an existing file.txt.gz) and without running gzip at all.

A significant difference compared to gzip -k though is that there will be no attempt at copying the file.txt‘s metadata (ownership, permissions, modification time, name of uncompressed file) to file.txt.gz.

Also if file.txt.gz already existed, it will silently override it unless you have turned the noclobber option on in your shell (with set -o noclobber for instance in POSIX shells).

Answered By: Stéphane Chazelas

Answer 3

Note that the recently (June 2013) released gzip-1.6 "accepts the –keep (-k) option, for consistency with tools like xz, lzip and bzip2. With this option, gzip no longer removes named input files when compressing or decompressing".

Excerpt from the man page:

  -k --keep
         Keep (don't delete) input files during compression or decompression.

So, as of 1.6, you can use -k or --keep to keep the original file:

gzip -k -- "$file"

(note that it doesn’t work if $file is - (which gzip interprets as meaning stdin instead of the actual file called -), in which case, you have to change it to ./-)

That option was first introduced in the FreeBSD implementation of gzip (in FreeBSD 7.0 in 2007) for consistency with bzip2. That gzip is based on a rewrite of GNU gzip by NetBSD. The -k option eventually made it back to NetBSD in 2010.

Answered By: don_crissti

Answer 4

To build on @Matteo’s answer, you could make gzipkeep able to handle wildcards by surrounding the code in a for loop, preserving the ability that gzip has to handle multiple files at once on a system that lacks that -k flag (a huge advantage, otherwise, for -k). I also made it verbose so I could see the status of each attempted file:

gzipkeep() {
    for file in "$@"; do
        if [ -f "$file" ] ; then
            gzip -cv9 -- "$file" > "$file.gz"
        fi  
    done
}

Then just run it with a wildcard. For example:

gzipkeep images/*.svg

Answered By: Timothy R. Butler