From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:47299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hX0hK-0006C0-LM for guix-patches@gnu.org; Sat, 01 Jun 2019 05:53:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hX0bP-0007et-Ir for guix-patches@gnu.org; Sat, 01 Jun 2019 05:47:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:51798) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hX0bP-0007eg-Et for guix-patches@gnu.org; Sat, 01 Jun 2019 05:47:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hX0bO-0004sn-0f for guix-patches@gnu.org; Sat, 01 Jun 2019 05:47:03 -0400 Subject: [bug#35866] [PATCH] gnu: Add qtwebengine. Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20190523062344.20601-1-mrosset@bufio.org> <87zhn7pq0r.fsf@gnu.org> <87y32qii63.fsf@bufio.org> Date: Sat, 01 Jun 2019 11:46:13 +0200 In-Reply-To: <87y32qii63.fsf@bufio.org> (mrosset@bufio.org's message of "Tue, 28 May 2019 10:48:52 -0700") Message-ID: <877ea5k596.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: mrosset@bufio.org Cc: mike.rosset@gmail.com, 35866@debbugs.gnu.org Hello, mrosset@bufio.org skribis: > It seems to me that QT is already doing the right thing > here. Unfortunately I don't think it will be easy to reuse the > ungoogle-chrome code base. It would probably require manually re-basing > then applying qt patches. Also there is no clear benefit for it. Since > updating ungoogle-chromium would not directly benefit qtwebengine. In > short QT seems to already be doing the necessary work. I think this would require a careful analysis like the one Marius Bakke carried out when packaging =E2=80=98ungoogled-chromium=E2=80=99. It would be both nicer and easier if QtWebEngine could be tweaked to use our own =E2=80=98ungoogled-chromium=E2=80=99 directly instead of rebuilding= one, but yeah, that sounds tricky. > I can though now, do my best to ensure that the least amount of 3rd > party libraries are used. I'll update my patch as soon as possible. And > I will explore the chromium source issue more in the process. OK. Thank you! Ludo=E2=80=99.