[Top][All Lists]

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

Re: Licensing of dummy.c

From: Simon Josefsson
Subject: Re: Licensing of dummy.c
Date: Thu, 13 Sep 2012 15:56:09 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)

Reuben Thomas <address@hidden> writes:

> On 17 June 2012 16:40, Bruno Haible <address@hidden> wrote:
>> Hi Jim, Reuben,
>>> > Since this file is trivial, would it be possible to give it an
>>> > all-permissive license? Someone has just (helpfully!) pointed out that
>>> > it shouldn't be in a BSD-licensed project I maintain, where it gets
>>> > pulled in by bootstrap.
>>> If dummy's license is causing trouble, how can you use any
>>> nontrivial part of gnulib?
>> gnulib-tool is also meant to combine source code when all your modules
>> come from your own package (option --local-dir) and you use no modules
>> from gnulib.
>> The 'dummy' module is hardwired into gnulib-tool, therefore its license
>> needs to be permissive, like Reuben says. As the only non-trivial contributor
>> to lib/dummy.c, I am changing its license:
> This is great. I now need this, but I can't find out how to get
> gnulib-tool to generate the file with an all-permissive license (only
> with an LGPL license). Help?

This isn't supported now, but it might be useful.  How about a
gnulib-tool --license=foo instead of the current --lgpl?  I'm using some
files from gnulib in projects licensed under the BSD license (primarily
m4 macros), but I'm copying the files manually today.


reply via email to

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