[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor-browser-build/master] Add comment to explain why we build https-e once for all platforms
commit 84fd513bee8b345d636a3f9d6529fe683c40f0a1
Author: Nicolas Vigier <boklm@xxxxxxxxxxxxxx>
Date: Thu Aug 3 21:43:42 2017 +0200
Add comment to explain why we build https-e once for all platforms
---
projects/https-everywhere/config | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/projects/https-everywhere/config b/projects/https-everywhere/config
index 3652aaa..6ee1ee9 100644
--- a/projects/https-everywhere/config
+++ b/projects/https-everywhere/config
@@ -7,6 +7,14 @@ gpg_keyring: https-everywhere.gpg
tag_gpg_id: 1
filename: "[% project %]-[% c('version') %]-[% c('var/build_id') %].xpi"
var:
+ # HTTPS Everywhere is expected to be the same on all platforms. To avoid
+ # building the same thing 4 times, using 4 different container images
+ # (each one with a different suite or architecture), we set the container
+ # to wheezy/amd64 for all platforms. This allows us to create only one
+ # container image, and also build the extension only one time as the
+ # filename does not contain the platform, and var/build_id should be
+ # the same since there is now nothing platform specific in the build
+ # inputs. This allows us to save a little time and disk space.
container:
use_container: 1
suite: wheezy
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits