#!/bin/bash
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_UNVALIDATED="$PWD/pkg/rulesets.unvalidated.sqlite"
RULESETS_SQLITE="$PWD/src/defaults/rulesets.sqlite"
ANDROID_APP_ID=org.mozilla.firefox
[ -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" ] ; 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"
# When a file is renamed, the old copy can linger in the checkout directory.
# Ensure a clean build.
git clean -fdx
git submodule update --recursive -f
# 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"
cp $SUBDIR/pkg/$XPI_NAME-eff.xpi pkg/
if ! cp $SUBDIR/pkg/$XPI_NAME-amo.xpi pkg/ 2> /dev/null ; then
echo Old version does not support AMO
fi
rm -rf $SUBDIR
exit 0
fi
# Only generate the sqlite database if any rulesets have changed. Tried
# implementing this with make, but make is very slow with 15k+ input files.
needs_update() {
find src/chrome/content/rules/ -newer $RULESETS_UNVALIDATED |\
grep -q .
}
if [ ! -f "$RULESETS_UNVALIDATED" ] || needs_update ; then
# This is an optimization to get the OS reading the rulesets into RAM ASAP;
# it's useful on machines with slow disk seek times; doing several of these
# at once allows the IO subsystem to seek more efficiently.
for firstchar in `echo {a..z} {A..Z} {0..9}` ; do
# Those cover everything but it wouldn't matter if they didn't
nohup cat src/chrome/content/rules/"$firstchar"*.xml >/dev/null 2>/dev/null &
done
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 the unvalidated rulesets have changed, validate and copy to the validated
# rulesets file.
if [ "$RULESETS_UNVALIDATED" -nt "$RULESETS_SQLITE" ] ; then
bash utils/validate.sh
fi
# 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" ]; then
XPI_NAME="$XPI_NAME"
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
fi
# Prepare packages suitable for uploading to EFF and AMO, respectively.
[ -d pkg ] || mkdir pkg
[ -e pkg/xpi-eff ] && rm -rf pkg/xpi-eff
cp -a src/ pkg/xpi-eff/
cp -a translations/* pkg/xpi-eff/chrome/locale/
rm -r pkg/xpi-eff/chrome/content/rules
[ -e pkg/xpi-amo ] && rm -rf pkg/xpi-amo
cp -a pkg/xpi-eff/ pkg/xpi-amo/
# The AMO version of the package cannot contain the updateKey or updateURL tags.
# Also, it has a different id than the eff-hosted version, because Firefox now
# requires us to upload the eff-hosted version to an unlisted extension on AMO
# in order to receive a signature indicating that it is not malware.
# https://github.com/efforg/https-everywhere/issues/2051
sed -i.bak -e '/updateKey/d' -e '/updateURL/d' \
-e 's,