forked from EFForg/https-everywhere
-
Notifications
You must be signed in to change notification settings - Fork 0
/
makexpi.sh
executable file
·175 lines (152 loc) · 5.27 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
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
#!/bin/sh
set -o errexit
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 build from the current src directory.
#
# ./makexpi.sh
#
# OR, invoke with a tag name to build a specific branch or tag.
#
# e.g.:
#
# ./makexpi.sh 0.2.3.development.2
cd "`dirname $0`"
RULESETS_SQLITE="$PWD/src/defaults/rulesets.sqlite"
[ -d pkg ] || mkdir pkg
# If the command line argument is a tag name, check that out and build it
if [ -n "$1" ] && [ "$2" != "--no-recurse" ] && [ "$1" != "--fast" ] ; then
BRANCH=`git branch | head -n 1 | cut -d \ -f 2-`
SUBDIR=checkout
[ -d $SUBDIR ] || mkdir $SUBDIR
cp -r -f -a .git $SUBDIR
cd $SUBDIR
git reset --hard "$1"
# This is an optimization to get the OS reading the rulesets into RAM ASAP;
# it's useful on machines with slow disk seek times; there might be something
# better (vmtouch? readahead?) that tells the IO subsystem to read the files
# in whatever order it wants...
nohup cat src/chrome/content/rules/*.xml >/dev/null 2>/dev/null &
# Use the version of the build script that was current when that
# tag/release/branch was made.
./makexpi.sh $1 --no-recurse || exit 1
# The fact that the above works even when the thing you are building predates
# support for --no-recurse in this script is (1) non-intuitive; (2) crazy; and (3)
# involves two pristine checkouts of $1 within each other
# Now escape from the horrible mess we've made
cd ..
XPI_NAME="$APP_NAME-$1.xpi"
# In this mad recursive situation, sometimes old buggy build scripts make
# the xpi as ./pkg :(
if ! cp $SUBDIR/pkg/$XPI_NAME pkg/ ; then
echo Recovering from hair-raising recursion:
echo cp $SUBDIR/pkg pkg/$XPI_NAME
cp $SUBDIR/pkg pkg/$XPI_NAME
fi
rm -rf $SUBDIR
exit 0
fi
# Same optimisation
nohup cat src/chrome/content/rules/*.xml >/dev/null 2>/dev/null &
if [ "$1" != "--fast" -o ! -f "$RULESETS_SQLITE" ] ; then
echo "Generating sqlite DB"
python2.7 ./utils/make-sqlite.py
fi
# =============== BEGIN VALIDATION ================
# Unless we're in a hurry, validate the ruleset library & locales
die() {
echo >&2 "ERROR:" "$@"
exit 1
}
if [ "$1" != "--fast" ] ; then
if [ -f utils/trivial-validate.py ]; then
VALIDATE="python2.7 ./utils/trivial-validate.py --ignoredups google --ignoredups facebook"
elif [ -f trivial-validate.py ] ; then
VALIDATE="python2.7 trivial-validate.py --ignoredups google --ignoredups facebook"
elif [ -x utils/trivial-validate ] ; then
# This case probably never happens
VALIDATE=./utils/trivial-validate
else
VALIDATE=./trivial-validate
fi
if $VALIDATE src/chrome/content/rules >&2
then
echo Validation of included rulesets completed. >&2
echo >&2
else
die "Validation of rulesets failed."
fi
# Check for xmllint.
type xmllint >/dev/null || die "xmllint not available"
GRAMMAR="utils/relaxng.xml"
if [ -f "$GRAMMAR" ]
then
# xmllint spams stderr with "<FILENAME> validates, even with the --noout
# flag. We can't grep -v for that line, because the pipeline will mask error
# status from xmllint. Instead we run it once going to /dev/null, and if
# there's an error run it again, showing only error output.
validate_grammar() {
find src/chrome/content/rules -name "*.xml" | \
xargs xmllint --noout --relaxng utils/relaxng.xml
}
if validate_grammar 2>/dev/null
then
echo Validation of rulesets against $GRAMMAR succeeded. >&2
else
validate_grammar 2>&1 | grep -v validates
die "Validation of rulesets against $GRAMMAR failed."
fi
else
echo Validation of rulesets against $GRAMMAR SKIPPED. >&2
fi
if [ -x ./utils/compare-locales.sh ] >&2
then
if sh ./utils/compare-locales.sh >&2
then
echo Validation of included locales completed. >&2
else
die "Validation of locales failed."
fi
fi
fi
# =============== END VALIDATION ================
# The name/version of the XPI we're building comes from src/install.rdf
XPI_NAME="pkg/$APP_NAME-`grep em:version src/install.rdf | sed -e 's/[<>]/ /g' | cut -f3`"
if [ "$1" ] && [ "$1" != "--fast" ] ; then
XPI_NAME="$XPI_NAME.xpi"
else
# During development, generate packages named with the short hash of HEAD.
XPI_NAME="$XPI_NAME~`git rev-parse --short HEAD`"
if ! git diff-index --quiet HEAD; then
XPI_NAME="$XPI_NAME-dirty"
fi
XPI_NAME="$XPI_NAME.xpi"
fi
[ -d pkg ] || mkdir pkg
# Used for figuring out which branch to pull from when viewing source for rules
GIT_OBJECT_FILE=".git/refs/heads/master"
export GIT_COMMIT_ID="HEAD"
if [ -e "$GIT_OBJECT_FILE" ]; then
export GIT_COMMIT_ID=$(cat "$GIT_OBJECT_FILE")
fi
cd src
# Build the XPI!
rm -f "../$XPI_NAME"
#zip -q -X -9r "../$XPI_NAME" . "-x@../.build_exclusions"
python2.7 ../utils/create_xpi.py -n "../$XPI_NAME" -x "../.build_exclusions" "."
ret="$?"
if [ "$ret" != 0 ]; then
rm -f "../$XPI_NAME"
exit "$?"
else
echo >&2 "Total included rules: `sqlite3 $RULESETS_SQLITE 'select count(*) from rulesets'`"
echo >&2 "Rules disabled by default: `find chrome/content/rules -name "*.xml" | xargs grep -F default_off | wc -l`"
echo >&2 "Created $XPI_NAME"
if [ -n "$BRANCH" ]; then
cd ../..
cp $SUBDIR/$XPI_NAME pkg
rm -rf $SUBDIR
fi
fi