Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] qt5webengine: update chromium license file names
Date: Wed, 29 Aug 2018 22:32:42 +0200	[thread overview]
Message-ID: <20180829223242.31c40388@windsurf> (raw)
In-Reply-To: <20180829105124.14758-1-laurent.hartanerot@gmail.com>

Hello Laurent,

On Wed, 29 Aug 2018 12:51:24 +0200, Laurent Hartanerot wrote:
> From: Laurent Hartanerot <laurent.hartanerot@atos.net>
> 
> Add license file name for qt5webengine-5.6
> 
> Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net>

Thanks for this new iteration. Unfortunately, I still see a number of
problems, some of them dating back from the origin of the qt5webengine
package (so Ga?l if you're around, your feedback/help would be nice).

Laurent, the first issue is that when your patch is applied, legal-info
still doesn't work when the build wasn't done, i.e if you do "make
clean; make legal-info", it will fail with:

cp: cannot stat '/home/thomas/projets/buildroot/output/build/qt5webengine-5.6.3/src/3rdparty/chromium/third_party/WebKit/Source/build/scripts/license.pyc': No such file or directory

This is because you have added the license.pyc file in the list of
license files, but this file only gets created at build time. And
anyway, since it's Python byte-code, it's not very useful.

How was this list of license files generated ? It seems like all files
containing "copying" or "license" in their name were taken. But does it
make sense to include those license.py files ?

Another problem is that the legal-info for qt5webengine in version 5.11
is also broken:

cp: cannot stat '/home/thomas/projets/buildroot/output/build/qt5webengine-5.11.1/src/3rdparty/chromium/buildtools/third_party/libc++abi/trunk/LICENSE.TXT': No such file or directory

> +CHROMIUM_LICENSE_FILES = \

Another problem is the name of this variable: if we ever have a package
called "chromium" (which is not unlikely, as it was submitted in
https://patchwork.ozlabs.org/patch/942284/), then this
CHROMIUM_LICENSE_FILES variable internal to qt5webengine will clash
with the CHROMIUM_LICENSE_FILES of the legitimate chromium package.

So the naming of this variable should be changed to
QT5WEBENGINE_CHROMIUM_LICENSE_FILES or something like this.

> +ifeq ($(BR2_PACKAGE_QT5_VERSION_LATEST),y)
>  include package/qt5/qt5webengine/chromium.inc

Perhaps this file should be renamed chromium-latest.inc

> +else
> +include package/qt5/qt5webengine/chromium.5.6.inc

and this one chromium-lts.inc ?

Could you send a couple of separate patches to fix those issues ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-29 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  6:30 [Buildroot] [PATCH 1/1] qt5webengine: update chromium license file names Laurent Hartanerot
2018-08-29  8:24 ` Thomas Petazzoni
2018-08-29 10:45   ` Laurent Hartanerot
2018-08-29 10:51 ` [Buildroot] [PATCH v2 " Laurent Hartanerot
2018-08-29 20:32   ` Thomas Petazzoni [this message]
2018-08-30  6:13     ` Laurent Hartanerot
2018-09-01  8:02     ` Gaël PORTAY
2018-08-30 10:05 ` [Buildroot] [PATCH v3 1/3] qt5webengine: update chromium license file names for qt-lts Laurent Hartanerot
2018-09-01 12:46   ` Thomas Petazzoni
2018-09-27 21:12   ` Peter Korsgaard
2018-08-30 10:06 ` [Buildroot] [PATCH v3 2/3] qt5webengine: update chromium license file names for qt-latest Laurent Hartanerot
2018-09-01 12:46   ` Thomas Petazzoni
2018-08-30 10:07 ` [Buildroot] [PATCH v3 3/3] qt5webengine: Rename internal variable to qt5webengine Laurent Hartanerot
2018-09-01 12:47   ` Thomas Petazzoni

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=20180829223242.31c40388@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox