diff options
| author | Stephen Blott | 2017-10-29 12:20:59 +0000 |
|---|---|---|
| committer | Stephen Blott | 2017-10-29 12:20:59 +0000 |
| commit | 69c3e8a4b8aef152a2c994c5da922a37ac3f5cf6 (patch) | |
| tree | 2c7f31821c9daca2335e383c0b189c76817cbca4 | |
| parent | b3c040f84b6ae44a3a79778e2435cf949f7e707b (diff) | |
| download | vimium-69c3e8a4b8aef152a2c994c5da922a37ac3f5cf6.tar.bz2 | |
Move FF package build into regular build process.
(Separately, these two processes may be doing the same thing.)
| -rw-r--r-- | Cakefile | 8 |
1 files changed, 3 insertions, 5 deletions
@@ -77,6 +77,9 @@ task "package", "Builds a zip file for submission to the Chrome store. The outpu spawn "rsync", rsyncOptions, false, true spawn "zip", ["-r", "dist/vimium-#{vimium_version}.zip", "dist/vimium"], false, true + spawn "zip", "-r -FS dist/vimium-ff-#{vimium_version}.zip background_scripts Cakefile content_scripts CONTRIBUTING.md CREDITS icons lib + manifest.json MIT-LICENSE.txt pages README.md -x *.coffee -x Cakefile -x CREDITS -x *.md".split(/\s+/), false, true + # This builds a CRX that's distributable outside of the Chrome web store. Is this used by folks who fork # Vimium and want to distribute their fork? task "package-custom-crx", "build .crx file", -> @@ -157,8 +160,3 @@ task "coverage", "generate coverage report", -> source: (Utils.escapeHtml fs.readFileSync fname, 'utf-8').split '\n' fs.writeFileSync 'jscoverage.json', JSON.stringify(result) - -task "zip", "build Firefox zip file in ../vimium.zip", -> - spawn "zip", "-r -FS ../vimium.zip background_scripts Cakefile content_scripts CONTRIBUTING.md CREDITS icons lib - manifest.json MIT-LICENSE.txt pages README.md -x *.coffee -x Cakefile -x CREDITS -x *.md".split /\s+/ - |