From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
wei.liu2@citrix.com, boris.ostrovsky@oracle.com, olaf@aepfle.de,
andrew.cooper3@citrix.com, dgdegra@tycho.nsa.gov,
anil@recoil.org, waldi@debian.org, dave.scott@citrix.com,
andryuk@aero.org, marmarek@invisiblethingslab.com,
mattjd@gmail.com, roger.pau@entel.upc.edu
Subject: libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license?
Date: Mon, 6 Jun 2016 17:36:23 -0400 [thread overview]
Message-ID: <20160606213623.GB16628@char.us.oracle.com> (raw)
Hey!
I picked the list of people on this email from the git log on tools/misc/libvchan/
(albeit this is about xen/include/public/io/libxenvchan.h).
The problem is that the 'COPYING' file in the root directory of Xen source
says:
"
Licensing Exceptions (the relaxed BSD-style license)
----------------------------------------------------
For the convenience of users and those who are porting OSes to run as
Xen guests, certain files in this repository are not subject to the
GPL when distributed separately or included in software packages
outside this repository."
The libxenvchan.h header file is an Lesser GPLv2.1. Which would
imply that one could ignore the giant @section LICENSE in the libxenvchan.h
and treat it as non-GPL...
But to make the matters more complicated the ./COPYING files continues
with:
"Instead we specify a much more relaxed
BSD-style license. Affected files include the Xen interface headers
(xen/include/public/COPYING), MiniOS (extras/mini-os) and various
drivers, support functions and header files within Xen-aware Linux
source trees. In all such cases, license terms are stated at the top
of the file or in a COPYING file in the same directory. Note that
_any_ file that is modified and then distributed within a Linux kernel
is still subject to the GNU GPL. "
Great, so if I break this up:
a) "Xen interface headers (xen/include/public/COPYING),"
b) "MiniOS (..) and various drivers,"
c) "support functions and header files with Xen-aware Linux
source trees."
Well, libxenvchan is a).
What?
Yes, if I look in xen/include/public/COPYING it says:
"
XEN NOTICE
==========
This copyright applies to all files within this subdirectory and its
subdirectories:
include/public/*.h
include/public/hvm/*.h
include/public/io/*.h
The intention is that these files can be freely copied into the source
tree of an operating system when porting that OS to run on Xen. Doing
so does *not* cause the OS to become subject to the terms of the GPL
"
and libxenvchan.h is in ./xen/include/public/io/libxenvchan.h
Also it is in FreeBSD (source tree): ./sys/xen/interface/io/libxenvchan.h
That looks to be an oversigh. The commit that introduced the file is:
commit 1a16a3351ff2f2cf9f0cc0a27c89a0652eb8dfb4
Author: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Date: Thu Oct 6 19:44:40 2011 +0100
libvchan: interdomain communications library
As such I was wondering if the folks who wrote/checked the file in
could weight in on what their intention was in regards to this file?
Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-06 21:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:36 Konrad Rzeszutek Wilk [this message]
2016-06-07 13:36 ` libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license? Konrad Rzeszutek Wilk
2016-06-07 15:54 ` Ian Jackson
2016-06-07 20:47 ` Marek Marczykowski-Górecki
2016-06-09 14:21 ` [PATCH for 4.7] libxenvchan: Change license of header from Lesser GPL v2.1 to BSD Konrad Rzeszutek Wilk
2016-06-09 14:30 ` Wei Liu
2016-06-09 15:10 ` Konrad Rzeszutek Wilk
2016-06-09 15:12 ` Ian Jackson
2016-06-09 15:16 ` Daniel De Graaf
2016-06-09 15:23 ` Marek Marczykowski-Górecki
2016-06-09 16:34 ` Jason P Andryuk
2016-06-09 16:37 ` Anil Madhavapeddy
2016-06-09 15:27 ` Olaf Hering
2016-06-09 16:36 ` Wei Liu
2016-06-09 15:35 ` George Dunlap
2016-06-09 15:37 ` Roger Pau Monné
2016-06-09 15:43 ` Ian Jackson
2016-06-10 10:33 ` Ian Campbell
2016-06-10 13:07 ` Ian Jackson
2016-06-10 13:31 ` Konrad Rzeszutek Wilk
2016-06-10 14:58 ` Wei Liu
2016-06-13 9:28 ` [PATCH v2 hopefully " Konrad Rzeszutek Wilk
2016-06-13 10:28 ` Wei Liu
2016-06-10 15:00 ` [PATCH " Ian Campbell
2016-06-09 15:44 ` Andrew Cooper
2016-06-09 16:19 ` Ian Jackson
2016-06-10 13:08 ` Ian Jackson
2016-06-09 16:45 ` Olaf Hering
2016-06-09 16:57 ` Wei Liu
2016-06-09 17:00 ` Olaf Hering
2016-06-10 7:04 ` Jan Beulich
2016-06-10 10:24 ` Matthew Daley
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=20160606213623.GB16628@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=andryuk@aero.org \
--cc=anil@recoil.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dave.scott@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=mattjd@gmail.com \
--cc=olaf@aepfle.de \
--cc=roger.pau@entel.upc.edu \
--cc=waldi@debian.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).