CGAL users discussion list

[Maria Dubrovskaya <>]

Phil,
the question is still not about LGPL'd library code itself, but about my own code. Is the person who created not just another modification, but an _official_ improvement (the last official library version) still responsible for making sure it works correctly with my application or I must do it myself in this case?

Best wishes,

Maria

On Fri, Feb 12, 2016 at 2:47 PM, Phil Weir <> wrote:

On 02/12/2016 11:21 AM, Maria Dubrovskaya wrote:

Hello Patric and Phil,

Yes, Patric, you mostly explained to me what I missed. However, the user can fail using my application with another version of the library, cause it's API can be changed in theory.
That is what I meant in my 2nd point. As you mentioned, 'forward-compatible API'.

As Phil said, making sure the improvements work correctly with my application is the modifier's responsibility. It's clear now. But what about the official last library's version?

Copyright license applies specifically to a piece of code, rather than a project, so you would be responsible for the piece of code (i.e. the exact version) you distribute. Future versions released by CGAL have no connection to that. Additionally, while a license is allowed to change in later versions (as it did between 3.x and 4.x), the LGPL license with your version's code is irrevocable [1], so your reference remains whatever it says in the version of the library you distribute. Of course, I am just commenting on the GPL aspects -- as I'm not a lawyer (IANAL) nor a member of the CGAL Project, you should double-check any ambiguous decisions with somebody qualified! Similarly, Patric and others, please comment if you feel anything here is not as expected.

All the best,
Phil

1 - http://www.groklaw.net/article.php?story=2006062204552163

--
You are currently subscribed to cgal-discuss.
To unsubscribe or access the archives, go to
https://sympa.inria.fr/sympa/info/cgal-discuss