On Thu, Jun 15, 2017 at 3:50 PM Jim Apple <jbap...@cloudera.com> wrote:
> Thank you for the responses. > > >> 5. Make sure the Whimsy page applies to all projects. For instance, > >> Impala releases are source tarballs, so if "Binary Distribution > >> Licensing" means something about a non-source-tarball release > >> artefact, it's not meaningful for Impala. > >> > > > > Hmm that's interesting. The ASF only releases source code. However, the > > second check is that your resulting binary is also compliant. > > The "your resulting binary" is for projects that distribute > convenience binaries? > No - but either way Impala is probably in the clear. The resulting binary is an issue if: - You use statically linked libraries (e.g. they get embedded in the binary) - You do provide a distribution style binary that includes them in the package (e.g. a rpm or deb or tar or zip) As an example, ActiveMQ Artemis depends on an optional extension for libaio. libaio is LGPL licensed. This binary is OK because it is optional, the user has to do something to enable it. But do note they ship it as a convenience. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
