Compress package tarballs with gzip

Tar files are conventionally compressed, often with gzip.  xz would be
better but is not as universally supported; in particular,
grunt-contrib-compress doesn't support it.
This commit is contained in:
Benjamin Gilbert 2013-04-22 20:13:42 -04:00
parent ee02dda56e
commit d7224f8206
2 changed files with 4 additions and 4 deletions

View File

@ -92,7 +92,7 @@ module.exports = function(grunt) {
},
tar: {
options: {
archive: "build/openseadragon.tar"
archive: "build/openseadragon.tar.gz"
},
files: [
{ expand: true, cwd: "build/", src: [ "openseadragon/**" ] }
@ -177,7 +177,7 @@ module.exports = function(grunt) {
// ----------
// Package task.
// Builds and creates the .zip and .tar files.
// Builds and creates the .zip and .tar.gz files.
grunt.registerTask("package", ["build", "compress"]);
// ----------

View File

@ -6,7 +6,7 @@ See it in action at http://openseadragon.github.io/.
## Stable Build
The latest stable builds are here: [Zip](http://openseadragon.github.io/openseadragon.zip) or [Tar](http://openseadragon.github.io/openseadragon.tar).
The latest stable builds are here: [Zip](http://openseadragon.github.io/openseadragon.zip) or [Tar](http://openseadragon.github.io/openseadragon.tar.gz).
## First Time Setup
@ -42,7 +42,7 @@ You can also publish the built version to the site-build repository. This assume
grunt publish
... which will delete the existing openseadragon folder, along with the .zip and .tar files, out of the site-build folder and replace them with newly built ones from the source in this repository; you'll then need to commit the changes to site-build.
... which will delete the existing openseadragon folder, along with the .zip and .tar.gz files, out of the site-build folder and replace them with newly built ones from the source in this repository; you'll then need to commit the changes to site-build.
## Testing