aboutsummaryrefslogtreecommitdiffstats
path: root/Cakefile
diff options
context:
space:
mode:
authorIlya Sukhar2013-05-18 21:00:18 -0700
committerIlya Sukhar2013-05-18 21:00:18 -0700
commit11031398af6c4981454354fb1a70cb3473368515 (patch)
tree034afb7ab7aaa1e27ebfa985a6b2077a39a771e3 /Cakefile
parent37471a33e66e05cb345d81374e1920d865c71253 (diff)
downloadvimium-11031398af6c4981454354fb1a70cb3473368515.tar.bz2
Pull the version in packaging
Diffstat (limited to 'Cakefile')
-rw-r--r--Cakefile4
1 files changed, 3 insertions, 1 deletions
diff --git a/Cakefile b/Cakefile
index d0b3acaf..d38fa425 100644
--- a/Cakefile
+++ b/Cakefile
@@ -54,6 +54,8 @@ task "package", "Builds a zip file for submission to the Chrome store. The outpu
# To get exec-sync, `npm install exec-sync`. We use this for synchronously executing shell commands.
execSync = require("exec-sync")
+ vimium_version = JSON.parse(fs.readFileSync("manifest.json").toString())["version"]
+
invoke "build"
execSync "rm -rf dist/vimium"
@@ -66,7 +68,7 @@ task "package", "Builds a zip file for submission to the Chrome store. The outpu
blacklist.map((item) -> ["--exclude", "'#{item}'"]))
execSync "rsync " + rsyncOptions.join(" ")
- execSync "cd dist && zip -r vimium.zip vimium"
+ execSync "cd dist && zip -r vimium-#{vimium_version}.zip vimium"
# 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?