WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [ANNOUNCE] xen ocaml tools

To: Jun Koi <junkoi2004@xxxxxxxxx>, Vincent Hanquez <Vincent.Hanquez@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [ANNOUNCE] xen ocaml tools
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 17 Feb 2009 07:59:58 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 17 Feb 2009 00:00:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdaac4d50902161719g545c3f07w525ccda5b933671b@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmQndw6LOGWIgC1SkaWFzYKy48CuAAN93Ij
Thread-topic: [Xen-devel] [ANNOUNCE] xen ocaml tools
User-agent: Microsoft-Entourage/12.15.0.081119
On 17/02/2009 01:19, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:

>> libxenctrl is using the GPL license, whereas we chose the LGPL license with
>> ocaml static exception everywhere.
> 
> This part is interesting!
> 
> I have some doubts here: for ex, now I want to reimplement some parts
> of libxenstore in BSD or LGPL. But I cannot avoid to include
> "/usr/include/{xs,xenctrl|.h", because they have some must-have data
> definition. But it seems all these headers are in GPL, so my code
> violates the copyright! Or not??

I think as long as the boilerplate and formatting is your own, the actual
meat of the struct definitions you could take and relicense without really
any issue. Since as you say there is really no other way those definitions
could be written.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel