2

I am planning to binary-include(only to package it into release in build, not include it in the source) an EPL v1.0 library in my Apache 2.0 project.

What I will do are:

  • ensure the lib is not code/binary placed in source code
  • clarify that in the released package, this lib is included and the lib is under EPL v1.0
  • license the project in Apache 2.0

Is this correct? If possible, could I have any examples(projects) on doing so to be referred :).

Thanks a lot!

ref:

Improve this question
4
  • 2
    The linked question is clear that "you cannot re-license unmodified EPL-ed code under the Apache 2 license. However, you can very well have them side-by-side in your project". Does this not answer your question? If not, what uncertainty remains?
    – MadHatter ♦
    Jul 7, 2022 at 8:58
  • Thanks, @MadHatter :). The main uncertainty for me was my case is for EPL v1 rather than v2. I will put it side-by-side and cite it in a license.[md|txt] file.
    – Wey Gu
    Jul 8, 2022 at 10:33
  • 1
    Thank you for your courteous reponse! The v1/v2 issue seems a legitimate one to me, although I think the linked answer doesn't depend on anything v2-specific in its analysis, and so would still apply. Are you happy that your question has been answered, and if so, should I close this a a duplicate of the linked one?
    – MadHatter ♦
    Jul 8, 2022 at 10:41
  • Dear @MadHatter, Thanks :) I am good with closing it with duplicated being marked, also your comment emphasizing the first ref is not v2-specific will help newcomers know the answer clearly, too.
    – Wey Gu
    Jul 10, 2022 at 7:09

0

Reset to default

Browse other questions tagged or ask your own question.