summaryrefslogtreecommitdiffstats
path: root/wiki/src/contribute/release_process/tor-browser.mdwn
diff options
context:
space:
mode:
authoranonym <anonym@riseup.net>2016-02-10 21:02:39 +0100
committeranonym <anonym@riseup.net>2016-02-11 00:19:21 +0100
commita8021ec093b62026e10e752dc1c0f5fb066e6bf7 (patch)
treeb93b3760ce907c6dc5fa67cd62c6ed3a1b628c71 /wiki/src/contribute/release_process/tor-browser.mdwn
parent4173d78b97ad598aba59c91e7c742b8892a8341c (diff)
Do the fontconfig dance with all browsers.
I.e. also the Unsafe and I2P Browser's. The main reason is so we do not need different images for these and the Tor browser in the automated test suite. One may argue, though, that for the Unsafe Browser this list of fonts would be fingerprintable, but I would be surprised if it already isn't so due to the Tor Browser Firefox patches.
Diffstat (limited to 'wiki/src/contribute/release_process/tor-browser.mdwn')
-rw-r--r--wiki/src/contribute/release_process/tor-browser.mdwn6
1 files changed, 4 insertions, 2 deletions
diff --git a/wiki/src/contribute/release_process/tor-browser.mdwn b/wiki/src/contribute/release_process/tor-browser.mdwn
index 071fc53..d8faca0 100644
--- a/wiki/src/contribute/release_process/tor-browser.mdwn
+++ b/wiki/src/contribute/release_process/tor-browser.mdwn
@@ -94,8 +94,10 @@ the corresponding tarballs ourselves, so read on the next section.
Sync with the start-tor-browser script
======================================
-Adapt our `config/chroot_local-includes/usr/local/bin/tor-browser` for
-recent changes in `RelativeLink/start-tor-browser` in the
+Adapt our `config/chroot_local-includes/usr/local/bin/tor-browser`
+and/or
+`config/chroot_local-includes/usr/local/lib/tails-shell-library/tor-browser.sh`
+for recent changes in `RelativeLink/start-tor-browser` in the
[Tor Browser Bundle Git repo](https://git.torproject.org/builders/tor-browser-bundle.git). Look
in the Git history: