From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1depOe-0006D3-3N for guix-patches@gnu.org; Mon, 07 Aug 2017 17:17:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1depOY-0002FM-SD for guix-patches@gnu.org; Mon, 07 Aug 2017 17:17:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42115) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1depOY-0002Eu-Jr for guix-patches@gnu.org; Mon, 07 Aug 2017 17:17:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1depOY-00076k-F5 for guix-patches@gnu.org; Mon, 07 Aug 2017 17:17:02 -0400 Subject: [bug#28004] Chromium Resent-Message-ID: From: Marius Bakke In-Reply-To: <20170807202341.5c54jx4mpudor47i@abyayala> References: <87y3qvb15k.fsf@fastmail.com> <20170807202341.5c54jx4mpudor47i@abyayala> Date: Mon, 07 Aug 2017 23:16:36 +0200 Message-ID: <87shh3axjf.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: ng0 Cc: 28004@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable ng0 writes: > Hi Marius, > > Marius Bakke transcribed 43K bytes: >> Hello Guix! >>=20 >> Attached is a patch for Chromium, a popular web browser. > > Nice! I've been using this from your branch for a while now, > works just fine :) > Is this not affected by the chromium discussion which happened > a while back? Can we include this? I'm all for this, because I > mainly use it for websites where firefox/icecat doesn't work so > well, and building it locally takes a very long time. I believe this is within the Free System Distribution Guidelines. DRM ("Widevine") is disabled at build time, and the Web Store is non-functional without the end user explicitly enabling it. There are some grey areas though. The browser may interact with certain non-free APIs (apart from regular browser duties) such as translation or prediction services. These features are optional, but some are enabled by default, and difficult to maintain patches for (I've tried). However, I have verified that it does not send any unsolicited requests with the current command-line options, apart from the very first launch which spawns a login prompt (help wanted!). Without either of those flags the browser "calls home" every time it starts. >> Note that I cannot guarantee timely delivery of security updates. Major >> version upgrades are hugely painful, and almost always contain many >> high-severity fixes. Should we mention that in the description? >>=20 >> Happy for any feedback. >>=20 > > Shouldn't you mention defines in addition to the define-public aswell, > or don't we do that? Not for new files (modules), typically. I don't think Magit can fill out those variable names (by pressing C on the hunks) either ;-) But it should probably go in web-browsers.scm anyway. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlmI2LQACgkQoqBt8qM6 VPq/MQgAjq8CBcZi+jDFnJsWC6UuBVsJ4YMgfkApERqAnVFxLCgylPM012u50HB1 cI6bj7G1r8x6yIHG77wex1H0aI764AOIamGHpZAzCbaAOQq9kiY6xpvkSWW4i2b9 WkJus2l/kNMKRJmF+qDOCUj9CGotYTX2Hr+JvSA0j1mXWGBRQcWKuOM7oZMKu76u I0E3MlRlenaAZ3lMatl7gfxmDTwbCgu3npkSXxN9h4CGp58QEEeMDb1bJxx3MpM+ VWWF56SnUkAzdVr/bYvV2oV/ZW5vrBNT4OqkhQXUtXyOZ+RXiGwdbF1mN1YVrKVo InjpK7QSOh8MV53gIx+INT0izAEm+w== =rqKg -----END PGP SIGNATURE----- --=-=-=--