Re: [Help-glpk] [Fwd: Help Needed]

[Noli Sicad]

> Did you mean "proprietary"? "Commercial" does not necessarily mean
> "proprietary".

Yes. "proprietary".

> Noli, please see the faq on the GPL:
> http://www.gnu.org/licenses/gpl-faq.html
> There are many nuances on how one can combine GPL'ed software.

We have discussion on issues on QGIS (GPL) forum. QGIS is GIS application.

Since the glpk java binding are free software distributed under the GNU GPL v3.

No question, it is all GPL.

However, if somebody releases source code /app that is LGPL, just to
interface with the interface solver (e.g. jar), then this is another
story.

GPL project + app that interface to GPL program (LGPL) + app that uses
the interface LGPL = "can be released a proprietary".

The GPL project source codes are "intacted" and also app that is
interface to GPL program as  distributed as LGPL.

It can be seen as:

GPL project + app (A) that interface to GPL program (LGPL) = GPL

App (A) that interface to GPL program (LGPL) + your code app = OK to
release as non-GPL.

Since the GPLK and Java API language binding are GPL, then scenario
mentioned above is out of the question.

Noli








On 4/10/12, Andrew Makhorin <address@hidden> wrote:
>> Xypon, What is the license of GLPK Java utility JAR file?
>>
>> The jar file is not linked to native solver, right? It is just
>> interface to the solver.
>>
>> Here my take on this issue.
>>
>> ############
>>
>> GLPK native solver is GPL.
>>
>> C programs + GPLK (GPL) solver = Your Application (GPL).
>>
>> If  GLPK Java utility JAR file is:
>>
>> 1. GLPK Java Jar (LGPL) + GPLK (GPL) solver + your code = Your app is
>> OK to be released as LGPL /MIT / BSD / ( commercial).
>
> Did you mean "proprietary"? "Commercial" does not necessarily mean
> "proprietary".
>
>>
>>
>> 2. GLPK Java Jar (GPL) + GPLK (GPL) solver + your code = GPL.
>>
>> It is not OK to distribute your application without releasing all the
>> source code (GPL).
>>
>
> Noli, please see the faq on the GPL:
> http://www.gnu.org/licenses/gpl-faq.html
> There are many nuances on how one can combine GPL'ed software.
>
>