[Xapian-discuss] Re: [Swig-devel] license issue

[Sam Liddicott]

Sorry for top posting again.
Lets check CVs to be sure that the license boilerplate was added by Richard and not me or David.

I'm thinking it was me and that I did it to make sure the generated code would be fully compatable with the PHP license - I rewrote the php generator so in order to generate a xapian module but then I wasn't figuring on that module being regenerated with xapian but to be stored in the cvs of php itself.

There is tiny boilerplate C, enough to actually register as a php module, but I don't see why the boilerplate text in the BsD licensed php module generator can't be changed as long as the new text can be legally applied to new generated code, which I think it can.

Sam

-----Original Message-----
From: "Olly Betts" <olly at survex.com>
To: "Sam Liddicott" <sam at liddicott.com>
Cc: "Xapian Discussion" <xapian-discuss at lists.xapian.org>; "William S Fulton" <wsf at fultondesigns.co.uk>; swig-devel at lists.sourceforge.net
Sent: 23/08/07 14:16
Subject: Re: [Xapian-discuss] Re: [Swig-devel] license issue

On Thu, Aug 23, 2007 at 02:06:54PM +0100, Sam Liddicott wrote:
> William, I think we can easily change the license emitted by the code
> generator for the php module.
> 
> Olly, until then I think it is fine to edit the generated code and
> change the license. The xapian authors are the ones licensing the code
> there.

The generated file contains code from SWIG too though.

I suspect the inclusion of the PHP licence boilerplate wasn't fully
though through, but it could be that Richard Palmer made use of code
from PHP itself which had that licence, and that this code can get
inserted into the generated file, so just removing the licence seems
unwise.  Similarly, I don't think it's wise to just remove it from
SWIG unless we have a firm idea why it was added in the first place.

I found another old address for Richard at uchicago.edu which also
bounces.  But does that mean that Dave Beazley might know him?

Cheers,
    Olly