On Sun, Feb 01, 2009 at 11:55:49AM +0100, Sylvain Beucler wrote:
> This issue was raised upstream but hasn't been resolved (and
> probably can't at their level):
> http://trac.xapian.org/ticket/191
We managed to find the SWIG code contributor who added the code to SWIG
which was inserting the PHP 2.02 licence boilerplate into the generated
wrapper and he was happy to remove that, which means we no longer have
both GPL and PHP licences in the SWIG-generated source file, which was
the original report there. But as the later comments say, there are
still unresolved licence compatibility issues.
I'm afraid that ticket seems to have dropped off my radar after getting
that resolved - thanks for bringing it up again.
There's code in Xapian which the current developers don't own the
copyright to, so any solution requiring relicensing Xapian isn't
possible, or at least not in the near future (at some point all of that
code may get replaced).
> It would nice to:
>
> - check with debian-legal to confirm
Have you done so since filing this bug? (Sorry for the delay in
responding, BTW - I was away on holiday).
> - contact the PHP community so they convert these naming
> restrictions into a proper trademark, making the copyright
> license GPL-compatible (like other scripting languages)
I think it would need to be the PHP Group rather than the community -
it's them who own the copyright.
A trademark would indeed be a saner way to "defend" the name PHP (since
it would cover non-derived software too).
It's a shame they dropped the GPL dual-licensing that PHP3 had as that
would have made this a non issue.
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
