On 26/03/2015 01:58, Marvin Humphrey wrote:
If it comes down to it, embedding the full ALv2 text and the content of
Charmonizer's NOTICE in the `charmonizer.c` amalgam file is preferable to
having users worry about LICENSE/NOTICE.

I don't think that will be necessary though.

[...]

I think the ALv2 might be fine, though.  The charmonizer.c amalgam is a
self-contained application.  It does not affect the licensing of products
built with it or distributed alongside it.

I also think that the NOTICE files of Lucy and Clownfish should mention
Charmonizer. See

http://www.apache.org/dev/licensing-howto.html#alv2-dep

Hmm, let's see.  As the primary author of that HowTo, I feel comfortable
asserting that its formula does not apply in this specific case...

*   The licensing of the Lucy library is not affected by the licensing of the
     charmonizer.c amalgam, any more than Apache HTTPD is affected by the
     Autoconf-generated `configure` script which it ships with.
*   The licensing of the Lucy library is also not affected by the licensing of
     `charmony.h` even though that file gets included.  It's basically just
     configuration output.  See Larry Rosen's comment on
     <https://issues.apache.org/jira/browse/LEGAL-141> for analysis.

Therefore, it is not necessary for the documentation of the Lucy library to
pass along the content of Charmonizer's NOTICE.  A work which includes
Charmonizer as a library would need to (this is the common case addressed by
the HowTo), but a work which interacts with Charmonizer as a separate
application and consumes its output does not.

I agree that the licensing of Charmonizer doesn't affect the licensing of the product built with it. Still, the meld.pl script concatenates parts of the Charmonizer source code without any changes. So I can't see how the ALv2 licensing terms wouldn't apply to the generated charmonizer.c and how distributing the code in charmonizer.c wouldn't require to comply with section 4 of the ALv2. This means that every project using Charmonizer

1. must distribute a copy of the ALv2.
2. must include the relevant portions of the Charmonizer NOTICE.

Nick

Reply via email to