Did the thread started in .general? Can you give a short summary? Gervase Markham wrote:
> I think Hixie's saying that if you want to combine with GPL code, you > have to change all the notices, as section 3 requires, before you can > do so. This is inconvenient (and may make returning changes to the > original codebase more complex.) That's a problem, but not that bad that it were the reason to dual-license under GPL instead of LGPL. There are quite a number of LGPL problems, and Mozilla code dual-licensed under the GPL could not be used in those projects, assuming they want to keep the ability to be used under LGPL terms. Note that this problem is (again!) a problem inherent with the LGPL and not limited to thedual license. If you want to use LGPL-"native" code in GPL projects, you have the same problem. It is unclear, how it works, if I don't directly incorporate/import the code into the GPL project, but just use it (e.g. linking, extracting mozilla tarballs etc.).
