RE: Clear up my License information

> Well, we are both right to a certain extent :)
> 
> The problem is that if your patch contains a modified line 
> that is only in
> the LGPL WineHQ tree, the 'viral' nature of the LGPL means 
> that one LGPL
> line causes the LGPL to apply to the whole patch, and thus cannot be
> duel-licensed (without permission of the author of the oiginal LGPL'ed
> line). How many times can I use the word LGPL in one sentance? Wow.
> :)

Note quite. First of all the LGPL is not quite that viral as the GPL.

The LGPL (unlike the GPL) even with its most restrictive interpretation
only applies to code that is either directly derived from LGPL code or
code that the LGPL work depends on for it functionallity.

Secondly the parts of the patch are seperatable (it is some sort of
aggregation)
since there is a + or a - or a space in the beginning of each line. LGPL
lines
with a space in the beginning of are unnessary context that is some meaning
could
be removed. The - lines are a little more problematic if some for copyright
relevant part of them exist in the + line. However if the + lines just
implement
a new function or new functionallity in some existing function without cut
and
pasting you are safe it is your code and it has not been derived from the
LGPL work.

Futhermore note that copyright only protects expression, specifically
"unique" expression,
so even you you indeed have cut and pasted some simple loop and slightly
modified it
you will get away with it. A noticeable part of some "unique" expression in
the LGPL:ed
part must remain otherwise it doesn't count.

So presumably unless it would take heavy surgery to make the patch apply it
wouldn't be
any problem for Rewind. On the other hand if it indeed took heavy surgery to
make the
patch apply it would be very likely that any "unique" LGPL:ed expression was
lost in the
heavy surgery process.

So no, save the work nessessary for Rewind to make any patch from X11
licenser apply I
don't see any problem from LGPL "contamintion" of the patches. In any case,
as I said
earlier this is Rewind problem, not the X11 licenser.