diff options
author | grizzlyuser <grizzlyuser@protonmail.com> | 2020-07-05 18:27:37 +0300 |
---|---|---|
committer | Andreas Grapentin <andreas@grapentin.org> | 2020-07-10 11:28:50 +0200 |
commit | e5bef2898d4f4c8bbc4a7ca745a1ea40651963f0 (patch) | |
tree | 4586c7acf493040973d16bb1b8addfd6ba5476b3 /pcr-testing/python-flufl-lock | |
parent | 37699250ec779951c3b984be6308a3b3b00ebdc8 (diff) | |
download | abslibre-e5bef2898d4f4c8bbc4a7ca745a1ea40651963f0.tar.gz abslibre-e5bef2898d4f4c8bbc4a7ca745a1ea40651963f0.tar.bz2 abslibre-e5bef2898d4f4c8bbc4a7ca745a1ea40651963f0.zip |
libre/iceweasel: Disable data reporting in build config
MOZ_SERVICES_HEALTHREPORT and MOZ_NORMANDY are two missing bits to
undefine MOZ_DATA_REPORTING, which is defined if any one of
healthreporting, crashreporting, telemetry reporting, or Normandy are
set. Crashreporting and telemetry reporting have been already disabled.
Some data reporting related preferences and code are enabled when
MOZ_DATA_REPORTING is defined, for example.
These "features" are for Mozilla users only, they don't make much sense
for Iceweasel users. Probably even harmful for them and Mozilla too,
because I don't think Mozilla is interested in data reporting spam from
non-Firefox users.
I'm not sure if these features can be classified as back doors or
spyware in GNU FSDG terms, but that's another thing to consider.
Also added a check that fails the build if some of those features are
not disabled in configuration.
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
Diffstat (limited to 'pcr-testing/python-flufl-lock')
0 files changed, 0 insertions, 0 deletions