www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Halliday (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LEGAL-192) Why is LGPL not allowed
Date Wed, 19 Feb 2014 21:04:19 GMT
Sam Halliday created LEGAL-192:

             Summary: Why is LGPL not allowed
                 Key: LEGAL-192
                 URL: https://issues.apache.org/jira/browse/LEGAL-192
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Sam Halliday

According to http://www.apache.org/legal/resolved.html the LGPL is not allowed because

  "The LGPL is ineligible primarily due to the restrictions it places on larger works, violating
the third license criterion. Therefore, LGPL-licensed works must not be included in Apache

where part three is

  "The license must not place restrictions on the distribution of larger works, other than
to require that the covered component still complies with the conditions of its license."

But I see no conflict here with regard to distribution. The license clearly states that software
which uses LGPL software can be distributed under whatever license the developer wishes:


The LGPL does, however, require that any changes to the LGPL component is released as LGPL
(including source code).

I have an LGPL library and there is a desire to see it included in an Apache project. Since
my project places no constraint on the distribution of the larger work, I do not see why I
should have to change the license in order to comply with these rules.

If I was using the GPL, I would see your point. But this is the LGPL and it appears to meet
your objectives.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message