From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44233) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1deoaJ-0006BI-Hq for guix-patches@gnu.org; Mon, 07 Aug 2017 16:25:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1deoaE-0000gw-As for guix-patches@gnu.org; Mon, 07 Aug 2017 16:25:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42078) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1deoaE-0000gY-7H for guix-patches@gnu.org; Mon, 07 Aug 2017 16:25:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1deoaD-0005ty-Sj for guix-patches@gnu.org; Mon, 07 Aug 2017 16:25:01 -0400 Subject: [bug#28004] Chromium Resent-Message-ID: Date: Mon, 7 Aug 2017 20:23:41 +0000 From: ng0 Message-ID: <20170807202341.5c54jx4mpudor47i@abyayala> References: <87y3qvb15k.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ujecsmtc47vy3x44" Content-Disposition: inline In-Reply-To: <87y3qvb15k.fsf@fastmail.com> 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: Marius Bakke Cc: 28004@debbugs.gnu.org --ujecsmtc47vy3x44 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. (Pro-tip: Don't offload from very powerful laptops to 10 year old computers with 2 cores ;)) > It requires the new ld wrapper from 'core-updates' and a very powerful > build machine (a quad-core Sandy Bridge Xeon uses 2-3 hours). But to notice: it builds with less than 3GB RAM. > 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? --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --ujecsmtc47vy3x44 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmIzE0ACgkQ4i+bv+40 hYgyExAAjy+7Xrssgze/xnwH7xII69/0vvrBhg+pcEF0M7Qv6pvyaABa8y8/jZHN bgNo9YDb3e+CvGl40xKXypkrIdd4UH7Lv9iV3N4eoueUJJy7d8th/x/sU1crpltP ydKlLafzCCkZ1aWxhMJ1tvcbS3/Kl3DCgknToujlVMSK+YQM+qxl8R/rXkapA6Bt dQgy9LO7cpNvKmgldRSTaJI4OcyKnxkqFEz4wBSdhXpgOFXDM5KQCc1uFmo78eVJ o2LDsIy/lCjwVy7v7tEvQC0Bsg5BKmKhuj5yWitUT6je1dv2o6dNit0yn3X7rmHa bYl2CQ/AtSUZyXL09OwKIHeJDno0vVQJWSoR1KdcAdIprnebhWgK/BqnJ5PntqoS Z3y0MCZlj+IRtJnidI0aDGLMBrPcErRjNbrE8BvkLBa+COlgHqnEL/x8AFz37dx/ MF/J9jlF/3P4HHnqMVhXJPKgSflkOq8VpVPqFXCS9ILamgFOpUOlUn09/KwpHrWO gK+WFmfFbGBMW5U5XKrCjfnmpsM+C/Flink01N7pWTMFf+OqBt312eyIS4W1IKTx 8ENmQcpeu4hT9w1jbp3a1JdEW6xmLFTI1V3VLc+sc1CW7NCMiAEzPK+W9pHPDWKy 99qGyGel+kXI/kO6lbqrbe6SyW/dj/4JNmkLF3PzdbN4AbHP5p4= =Llsp -----END PGP SIGNATURE----- --ujecsmtc47vy3x44--