-
Notifications
You must be signed in to change notification settings - Fork 5
/
makexpi.sh
executable file
·79 lines (66 loc) · 2.32 KB
/
makexpi.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
#!/bin/sh
APP_NAME=https-everywhere
# builds a .xpi from the git repository, placing the .xpi in the root
# of the repository.
# invoke with no arguments to pull a prerelease of the current
# development point.
# invoke with the literal argument "uncommitted" to build from the
# current src directory.
# invoke with a tag name to build a specific branch or tag.
# e.g.:
# ./makexpi.sh 0.2.3.development.2
# or just:
# ./makexpi.sh
# BUGS: if you have a branch or tagged named "uncommitted" then this
# is kind of ambiguous. Also, the validation of rule syntax is done
# against the rules in the current directory, not necessarily the
# committed rules in git.
cd "$(dirname $0)"
if ./trivial-validate src/chrome/content/rules >&2
then
echo Validation of included rulesets completed. >&2
echo >&2
else
echo ERROR: Validation of rulesets failed. >&2
exit 1
fi
if [ -n "$1" ] && [ "$1" != "uncommitted" ]; then
VERSION="$1"
TARG="$1"
else
VERSION="$(grep em:version src/install.rdf | sed -e 's/[<>]/ /g' | cut -f3)~pre"
TARG=HEAD
if [ "$1" != "uncommitted" ] && [ -n "$(git status src -s)" ] ; then
printf >&2 "\
WARNING: There are uncommitted changes in your current repostitory.
WARNING: These changes will not be included in the generated .xpi
WARNING: Run 'git status' for information about the uncommitted changes.
WARNING: Or, use 'makexpi.sh uncommitted' to include them in the build.
"
fi
fi
XPI_NAME="pkg/$APP_NAME-$VERSION.xpi"
[ -d pkg ] || mkdir pkg
cd "src"
if [ "$1" = "uncommitted" ]; then
printf >&2 "WARNING: using zip instead of git archive to build .xpi\n"
CHANGES="$(git status . -s)"
if [ -n "$CHANGES" ]; then
printf >&2 "WARNING: uncommitted changes were included:\n%s\n" "$CHANGES"
fi
# FIXME: is it really acceptable to reuse .gitignore to specify
# include patterns for /usr/bin/zip? It seems to work for our
# current patterns (2010-11-09)
zip -X -q -9r "../$XPI_NAME" . "-x@../.gitignore"
else
git archive --format=zip -9 "$TARG" . > "../$XPI_NAME"
fi
ret="$?"
if [ "$ret" != 0 ]; then
rm -f "../$XPI_NAME"
exit "$?"
else
printf >&2 "Total included rules: $(ls chrome/content/rules/*.xml | wc -l)\n"
printf >&2 "Rules disabled by default: $(grep -lr default_off chrome/content/rules | wc -l)\n"
printf >&2 "Created %s\n" "$XPI_NAME"
fi