all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: mike.rosset@gmail.com
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: qtwenengine anybody?
Date: Sun, 05 Jan 2020 06:59:45 -0800	[thread overview]
Message-ID: <87zhf2c5jy.fsf@gmail.com> (raw)
In-Reply-To: <87o8vmn6an.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 01 Jan 2020 23:46:56 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

> Does the code include DRM support, for example?  Does it phone home?
> Can we see the patches that upstream applied to the Chromium sources?
>

QtWebengine does not handle DRM at all. That is handled by a 3rd party
plugin called wildevine and would require guix to bundle that plugin.
Something I'm confident is not going to happen. As an added measure my
proposed qtwebengine declaration has pepper plugins disabled making it
impossible to load 3rd party plugins either way.

see https://doc.qt.io/qt-5/qtwebengine-features.html#html5-drm
for reference

In regards to QtWebEngine phoning home https://wiki.qt.io/QtWebEngine
states all google services have been removed. Nothing I've seen
indicates this is not the case.

In terms of patches. You can get a complete diff of chromium sources
by cloning qtwebengine recursively like so.

--8<---------------cut here---------------start------------->8---
git clone http://code.qt.io/qt/qtwebengine.git --recursive
--8<---------------cut here---------------end--------------->8---

Version 5.12.6 of qtwebengine is based on chromium sources 69.0.3497.128
to get a complete diff you can do this from the src/3rdpath directory.
you can then get a complete patch diff for version 5.12.6 like so.

--8<---------------cut here---------------start------------->8---
git diff origin/upstream-master origin/69-based
--8<---------------cut here---------------end--------------->8---

see https://wiki.qt.io/QtWebEngine/Rebase_on_New_Chromium for reference

Mike

  parent reply	other threads:[~2020-01-05 14:59 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 12:55 qtwenengine anybody? Hartmut Goebel
2019-12-16 13:42 ` Pierre Neidhardt
2019-12-16 14:13   ` mike.rosset
2019-12-16 14:15     ` Pierre Neidhardt
2019-12-16 15:19       ` mike.rosset
2019-12-16 15:22     ` Hartmut Goebel
2019-12-16 15:45       ` mike.rosset
2019-12-16 15:57         ` Hartmut Goebel
2019-12-16 17:09           ` mike.rosset
2019-12-16 17:29             ` Hartmut Goebel
2019-12-18 21:24               ` mike.rosset
2019-12-18 22:03                 ` Pierre Neidhardt
2019-12-18 22:30                   ` mike.rosset
2019-12-19 18:23                     ` Pierre Neidhardt
2019-12-19 19:47                       ` mike.rosset
2019-12-19 20:36                         ` Pierre Neidhardt
2019-12-20  0:16                           ` mike.rosset
2019-12-20 10:46                             ` Pierre Neidhardt
2019-12-20 10:53                               ` Pierre Neidhardt
2019-12-20 15:52                             ` [bug#35866] [PATCH 2/2] gnu: qtwebengine now uses pulseaudio Mike Rosset
2019-12-18 22:46                 ` qtwenengine anybody? Ricardo Wurmus
2019-12-20 10:49                 ` Pierre Neidhardt
2019-12-20 16:04                   ` mike.rosset
2019-12-20 16:16                     ` Pierre Neidhardt
2019-12-20 16:44                       ` mike.rosset
2019-12-31 13:48                         ` Pierre Neidhardt
2019-12-31 13:50                           ` Pierre Neidhardt
2020-01-01 17:34                             ` mike.rosset
2020-01-01 20:43                               ` Pierre Neidhardt
2020-01-01 22:30                                 ` mike.rosset
2020-01-02 12:29                                   ` Hartmut Goebel
2020-01-02 20:24                                     ` mike.rosset
2020-01-03 14:57                                       ` Hartmut Goebel
2020-01-05 16:10                                         ` mike.rosset
2020-01-05 16:47                                           ` Hartmut Goebel
2020-01-05 16:47                                             ` [bug#35866] " Hartmut Goebel
2020-01-01 22:46                                 ` Ricardo Wurmus
2020-01-02 10:52                                   ` Pierre Neidhardt
2020-01-05 14:59                                   ` mike.rosset [this message]
2020-01-05 19:52                                     ` Ricardo Wurmus
2020-01-06  5:11                                       ` mike.rosset
2020-01-06 19:23                                       ` Marius Bakke
2020-01-07  0:27                                         ` mike.rosset
2020-01-07 10:26                                           ` Hartmut Goebel
2020-01-07 19:28                                             ` mike.rosset
2020-01-11 17:39                                               ` Marius Bakke
2020-01-11 17:40                                                 ` Pierre Neidhardt
2020-01-11 18:19                                                   ` Mike Rosset
2020-01-11 18:28                                                     ` Pierre Neidhardt
2020-01-13 10:54                                                   ` Mike Rosset
2020-01-13 14:26                                                     ` Pierre Neidhardt
2020-01-13 18:37                                                       ` Mike Rosset
2020-01-11 18:14                                                 ` Mike Rosset
2020-01-07  8:09                                         ` Pierre Neidhardt
2020-01-07 19:14                                           ` mike.rosset
2020-01-07  8:12                                         ` Pierre Neidhardt
2020-01-07 22:49                                           ` Marius Bakke
2020-01-01 17:22                           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhf2c5jy.fsf@gmail.com \
    --to=mike.rosset@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.