From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: Bug-gnulib <bug-gnulib@gnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH RFC 00/10] Enable repository wide style checking
Date: Thu, 13 Aug 2015 12:27:29 -0600 [thread overview]
Message-ID: <55CCE191.4010206@redhat.com> (raw)
In-Reply-To: <CAFEAcA_-zGowiwgr18muW=9V9+z=Ts-fhHxXTg2ZGvUzBrO08g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3131 bytes --]
[adding the gnulib list]
On 08/13/2015 11:53 AM, Peter Maydell wrote:
> On 31 July 2015 at 17:30, Daniel P. Berrange <berrange@redhat.com> wrote:
>> Historically QEMU has relied on the checkpatch.pl script,
>> borrowed from Linux, to check coding style compliance on
>> patches which are submitted. For what it is designed for,
>> it does a reasonable job, but I feel that QEMU would benefit
>> from some more checking in this area, in particular checks
>> that run across the entire repository, not just new patches.
>>
>> Rather than attempt to replace checkpatch.pl, this series
>> illustrates how we can augment our existing style compliance
>> checking. This imports the infrastructure from GNULIB which
>> provides a 'syntax-check' target in the makefiles.
>
> I like this in principle, but I notice that the GNULIB
> infrastructure is GPLv3. I really would strongly prefer
> that we not introduce any GPLv3 code into QEMU's git tree.
> I don't want to get into trying to figure out whether
> part of our makefile or build infrastructure being GPLv3
> implies the generated binaries are GPLv3 or not; the simplest
> approach is just to not allow any GPLv3 code into the git repo.
>
> Is there no GPLv2 or GPLv2-or-later version of this code?
Looks like gnulib.git commit fb7fde6f6 was the one that upgraded
maint.mk to GPLv3+, on the grounds that building with GPLv3+ code does
not infect your binary (see also the arguments in Autoconf, Automake,
gcc... - but those tend to include an explicit exception clause to make
it clear). Then again, qemu also avoids use of Autoconf and Automake.
It's worth asking the gnulib folks for an opinion on whether relaxing
the license on maint.mk and GNUmakefile to explicitly go back to GPLv2+,
and/or explicitly add some explicit exception clause like gcc that makes
it clear that using these files to build does not taint the built
product. Personally, I see no problem with using GPLv3'd tools (after
all, qemu requires GPLv3 GNU make, and gcc is also GPLv3 although clang
can step around that one), but I also see your reluctance of even having
a file in the qemu.git repo that has a GPLv3 clause.
As one of the contributors to gnulib, I'm okay with my contributions to
the files being relaxed; but we either need FSF blessing or consent from
all contributors to the files in question, which could get a bit daunting:
$ git shortlog top/maint.mk build-aux/useless-if-before-free \
build-aux/vc-list-files | grep '^[^[:space:]]'
Akim Demaille (16):
Alfred M. Szmidt (2):
Assaf Gordon (1):
Daniel P. Berrange (1):
Eric Blake (54):
Gary V. Vaughan (4):
Giuseppe Scrivano (1):
Jim Meyering (174):
Jiri Denemark (1):
Joel E. Denny (2):
Jose E. Marchesi (5):
Karl Heuer (1):
Martin von Gagern (1):
Paul Eggert (4):
Peter Rosin (1):
Peter Simons (2):
Pádraig Brady (6):
Ralf Wildenhues (4):
Reuben Thomas (2):
Simon Josefsson (16):
Soren Hansen (1):
Stefano Lattarini (2):
Theophile Ranquet (1):
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-08-13 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 16:30 [Qemu-devel] [PATCH RFC 00/10] Enable repository wide style checking Daniel P. Berrange
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 01/10] tests: import GNULIB's syntax-check infrastructure Daniel P. Berrange
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 02/10] maint: remove double semicolons in many files Daniel P. Berrange
2015-08-13 17:57 ` Peter Maydell
2015-08-14 8:32 ` Daniel P. Berrange
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 03/10] maint: remove / fix many doubled words Daniel P. Berrange
2015-08-03 16:10 ` Max Reitz
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 04/10] maint: remove unused include for assert.h Daniel P. Berrange
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 05/10] maint: remove unused include for dirent.h Daniel P. Berrange
2015-07-31 16:30 ` [Qemu-devel] [PATCH RFC 06/10] maint: remove unused include for signal.h Daniel P. Berrange
2015-07-31 16:31 ` [Qemu-devel] [PATCH RFC 07/10] maint: remove unused include for strings.h Daniel P. Berrange
2015-07-31 16:31 ` [Qemu-devel] [PATCH RFC 08/10] maint: avoid useless "if (foo) free(foo)" pattern Daniel P. Berrange
2015-07-31 16:31 ` [Qemu-devel] [PATCH RFC 09/10] maint: add check for use of POSIX functions which are not reentrant safe Daniel P. Berrange
2015-07-31 16:31 ` [Qemu-devel] [PATCH RFC 10/10] maint: enable checking for qemu/osdep.h header usage Daniel P. Berrange
2015-08-13 17:53 ` [Qemu-devel] [PATCH RFC 00/10] Enable repository wide style checking Peter Maydell
2015-08-13 18:27 ` Eric Blake [this message]
2015-08-13 20:39 ` Peter Maydell
2015-08-14 9:57 ` Daniel P. Berrange
2015-08-14 10:30 ` Paul Eggert
2015-08-14 10:35 ` Peter Maydell
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=55CCE191.4010206@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=bug-gnulib@gnu.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).