[libvirt] [PATCH] run: license as LGPL

It makes no sense to prohibit reuse of the wrapper in other LGPL projects, since most of libvirt is designed to be LGPL. Of course, when using the wrapper to wrap a GPL program, the combined result is still effectively GPL, but that shouldn't force us to license the wrapper as GPL in isolation. * run.in: Relicense to LGPLv2+. --- Any objections to this? run.in | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/run.in b/run.in index 5063522..5d4a04c 100644 --- a/run.in +++ b/run.in @@ -2,18 +2,19 @@ # libvirt 'run' programs locally script # Copyright (C) 2012-2013 Red Hat, Inc. # -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. +# This library is free software; you can redistribute it and/or +# modify it under the terms of the GNU Lesser General Public +# License as published by the Free Software Foundation; either +# version 2.1 of the License, or (at your option) any later version. # -# This program is distributed in the hope that it will be useful, +# This library is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# Lesser General Public License for more details. # -# You should have received a copy of the GNU General Public License -# along with this program; If not, see <http://www.gnu.org/licenses/>. +# You should have received a copy of the GNU Lesser General Public +# License along with this library; If not, see +# <http://www.gnu.org/licenses/>. #---------------------------------------------------------------------- # -- 1.8.1.2

On Fri, Feb 22, 2013 at 05:19:15PM -0700, Eric Blake wrote:
It makes no sense to prohibit reuse of the wrapper in other LGPL projects, since most of libvirt is designed to be LGPL. Of course, when using the wrapper to wrap a GPL program, the combined result is still effectively GPL, but that shouldn't force us to license the wrapper as GPL in isolation.
* run.in: Relicense to LGPLv2+. ---
Any objections to this?
This is fine. I will apply a similar change to libguestfs. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

On 02/23/2013 12:59 AM, Richard W.M. Jones wrote:
On Fri, Feb 22, 2013 at 05:19:15PM -0700, Eric Blake wrote:
It makes no sense to prohibit reuse of the wrapper in other LGPL projects, since most of libvirt is designed to be LGPL. Of course, when using the wrapper to wrap a GPL program, the combined result is still effectively GPL, but that shouldn't force us to license the wrapper as GPL in isolation.
* run.in: Relicense to LGPLv2+. ---
Any objections to this?
This is fine. I will apply a similar change to libguestfs.
Now pushed. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

Relicensed libguestfs run.in script: https://github.com/libguestfs/libguestfs/commit/1ca842d98b2da7fb3cd09e572c88... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
participants (2)
-
Eric Blake
-
Richard W.M. Jones