[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH RFC 00/10] Enable repository wide style checking

From: Peter Maydell
Subject: Re: [PATCH RFC 00/10] Enable repository wide style checking
Date: Thu, 13 Aug 2015 21:39:48 +0100

On 13 August 2015 at 19:27, Eric Blake <address@hidden> wrote:
> 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.

Right; we don't ship make or gcc in our code repo, and using
external-to-the-repository tools which happen to be GPLv3 is
obviously fine. Similarly, if you used the maint.mk script externally
as a tool which allowed you to find bugs which you submitted
patches to fix that wouldn't be a problem. I just don't want
a GPLv3-licensed file in the git repo and an integrated part
of our build-and-test system...

I would certainly appreciate a maint.mk with a GPLv2-or-later
license. Our other options are (a) use the last v2+ version
(which is what we do with our binutils disassemblers)
(b) do the style checks we care about some other way or
(c) don't bother doing the style checks at all.

(Incidentally we build fine with the GPLv2 GNU make 3.81, and we'll
continue to do so as long as that's the make that ships in OSX.
So the truly paranoid (among whom I don't count myself) can build
QEMU with no GPLv3 tooling at all.)

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]