Databases
StackOverflow2013
Postsdbo
POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
    primarykey
    data
    text
    <p>The Free Software Foundation considers <a href="http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses" rel="noreferrer">EPL and GPL to be incompatible</a>. Based on my reading of their reasoning, it would seem that the LGPL would be similarly affected -- IANAL, please correct me if that reading is incorrect. Now, there is a <a href="http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs" rel="noreferrer">guide for the copyright holder of the GPL-ed code</a> to provide exceptions allowing for the code to be linked against incompatible libraries, but it'd still preclude linking to GPL-ed code from others (if the code is already linked against an EPL library), and the situation with linking a GPL-ed program against an EPL <em>and</em> another LGPL library seems unclear.</p> <p>I'd like to know the answer to several questions:</p> <ol> <li>What exactly is the restriction against linking a GPL-ed product against both an EPL library and an LGPL library? Is it not allowed without the LGPL copyright holder's explicit permission, as it would be with GPL, or is it allowed?</li> <li>Would an exception granted by the EPL copyright holder be sufficient? Such an exception was considered safe by Trolltech (now part of Nokia), when it used to license the Qt library using its own Qt Public License which is GPL-incompatible; and by the KDE project, whose libraries link against Qt and are released under the LGPL, while KDE apps are generally released under the GPL. The FSF's objection is due to "weak copyleft" and "choice of law clause" -- the former seems unobjectionable, if the EPL license holder grants an exception, but what sort of exception granted by the EPL copyright holder would satisfy the "choice of law clause" objection?</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDheeraj V.S.
    1. USmichel-slm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour wrote "it would seem that the LGPL would be similarly affected" - why do you think so. In my opinion the LGPL should have no problem with the EPL.
      singulars
      1. POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
      1. UShakre
    2. COThe FSF vaguely referred to "[EPL]'s weak copyleft and choice of law clause"; while the "weak copyleft" objection shouldn't affect LGPL (where the license does not affect other components), I'm not sure about the "choice of law" objection. I'm not overly worried about the license choice for any code I write that makes use of EPL libraries, I'm worried about what restrictions I have if I make use of EPL *and* other GPL / LGPL libraries. Thanks.
      singulars
      1. POEPL (Eclipse Public License), GPL (GNU Public License)/LGPL (Lesser GPL) and license exceptions?
      1. USmichel-slm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload