Am 2010-09-21 22:39, schrieb Simon Josefsson:
You are right: http://developer.kde.org/documentation/licensing/licensing.htmlAlso, any external GPL code that Simon links to needs to have the same exception. Is there any external GPL code?Well of course - KDE.I believe kdelibs is LGPL, so maybe you are OK. It depends on what parts of KDE is used.
Only the server links to Julius which is kdecore but in the current implementation it might link to kdeui through simonscenarios (which should be split in the future in a separate non gui part).
Other than that, we don't link to anything on the server afaik (Qt is LGPL).
This is getting ridiculously frustrating. It's not that I don't think it's an important issue but I guess if you'd gather all involved parties and ask them if the current setup would be ok I am pretty sure everyone would agree. Oh well I guess that just comes with the territory.I know the pain, I've ended up rewriting several projects because of license problems with earlier implementations. What I have learned is that you should react to license issues as soon as possible, or you'll end up investing a lot of work into something that needs to be redesigned.
True...
Interestingly, the japanese sourceforge page lists Julius license as "OSI Approved, Other/Proprietary License".I obviously can't hack this into simon 0.3.0 but for the next version, would it help if I split the Julius-interfacing part into a plugin that doesn't link to KDE? This would be the easiest option in my opinion but as I understand it it would mean to distribute the plugin seperately? If Julius is not "free" in Debian eyes this would mean that simon becomes pretty much useless to be honest.I don't really have an opinion whether it is free or not yet, but it looks complicated.
Best regards, Peter