From: "Ludovic Courtès" <ludo@gnu.org>
To: mrosset@bufio.org
Cc: mike.rosset@gmail.com, 35866@debbugs.gnu.org
Subject: [bug#35866] [PATCH] gnu: Add qtwebengine.
Date: Sat, 01 Jun 2019 11:46:13 +0200 [thread overview]
Message-ID: <877ea5k596.fsf@gnu.org> (raw)
In-Reply-To: <87y32qii63.fsf@bufio.org> (mrosset@bufio.org's message of "Tue, 28 May 2019 10:48:52 -0700")
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 ‘ungoogled-chromium’.
It would be both nicer and easier if QtWebEngine could be tweaked to use
our own ‘ungoogled-chromium’ 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’.
next prev parent reply other threads:[~2019-06-01 9:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 6:23 [bug#35866] [PATCH] gnu: Add qtwebengine mike rosset
2019-05-27 21:05 ` Ludovic Courtès
2019-05-28 17:48 ` mrosset
2019-06-01 9:46 ` Ludovic Courtès [this message]
2019-05-29 23:37 ` [bug#35866] Mike Rosset
2019-05-29 23:37 ` [bug#35866] [PATCH] gnu: qtwebengine: Do not use 3rd party libraries Mike Rosset
2019-05-31 19:28 ` Marius Bakke
2019-05-31 23:16 ` mrosset
2019-07-18 9:26 ` [bug#35866] [PATCH] gnu: Add qtwebengine Ricardo Wurmus
2019-10-06 15:45 ` Pierre Neidhardt
2019-10-07 15:49 ` mike.rosset
2019-07-24 14:06 ` Brendan Tildesley
2019-12-16 15:29 ` [bug#35866] " Hartmut Goebel
2019-12-16 16:02 ` mike.rosset
2019-12-16 18:01 ` Pierre Neidhardt
2019-12-18 20:32 ` [bug#35866] [PATCH] " Mike Rosset
2019-12-19 18:29 ` Pierre Neidhardt
2019-12-19 20:19 ` Ricardo Wurmus
2019-12-20 0:02 ` mike.rosset
2019-12-18 20:45 ` Mike Rosset
2019-12-31 13:10 ` Hartmut Goebel
2020-01-01 16:29 ` mike.rosset
2020-01-01 16:03 ` [bug#35866] [PATCH 1/4] " Mike Rosset
2020-01-01 16:03 ` [bug#35866] [PATCH 2/4] gnu: qtwebengine now uses pulseaudio Mike Rosset
2020-01-01 16:03 ` [bug#35866] [PATCH 3/4] gnu: qtwebengine: now uses system libvpx Mike Rosset
2020-01-01 16:03 ` [bug#35866] [PATCH 4/4] gnu: qtwebengine: separate substitution and configure phase Mike Rosset
2020-01-24 0:16 ` bug#35866: Status: [PATCH] gnu: Add qtwebengine Mike Rosset
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ea5k596.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35866@debbugs.gnu.org \
--cc=mike.rosset@gmail.com \
--cc=mrosset@bufio.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).