Build Apache HAWQ bianry tarball with third party libraries

[Radar Da lei <rl...@pivotal.io>]

Hi Roman,

I plan to build out an Apache HAWQ binary tarball for users to download, so
they can install HAWQ easier.

But this will require we include all the third party libraries in the
tarball(currently we requires user to manually install them on each node),
I'm not quite sure if this action have license or other issues.

Would you please give some advice? Thanks a lot.

Regards,
Radar

Re: Build Apache HAWQ bianry tarball with third party libraries

[Radar Da lei <rl...@pivotal.io>]

Thank you Roman.

This is very helpful, I will try to make a binary out for demo and review.
Before that, it won't be public available.

Regards,
Radar

On Wed, Nov 25, 2015 at 7:14 PM, Roman Shaposhnik <rv...@apache.org> wrote:

> On Tue, Nov 24, 2015 at 6:16 PM, Radar Da lei <rl...@pivotal.io> wrote:
> > Hi Roman,
> >
> > I plan to build out an Apache HAWQ binary tarball for users to download,
> so
> > they can install HAWQ easier.
> >
> > But this will require we include all the third party libraries in the
> > tarball(currently we requires user to manually install them on each
> node),
> > I'm not quite sure if this action have license or other issues.
> >
> > Would you please give some advice? Thanks a lot.
>
> I see you guys publishing two types of binary tarballs:
>    1. Nightly builds
>    2. Convenience binary associated with particular release of HAWQ
>
> In both cases it is extremely important to make sure you're
> not bundling any Cat X licensed binaries into the tarball
> (most of the time this means GPL). As long as you don't
> you should make sure that:
>     1. Nightly builds are NOT advertised outside of your
>     developer community. E.g. you can't link to them on
>     the Download page of the HAWQ's website, etc.
>
>     2. Convenience binary tarball is included in the formal
>     release vote.
>
> These are the basic rules. If you can give me a link to
> a tarball available on Jenkins I can give you more feedback
> on the content.
>
> Hope this helps.
>
> Thanks,
> Roman.
>

Re: Build Apache HAWQ bianry tarball with third party libraries

[Roman Shaposhnik <rv...@apache.org>]

On Tue, Nov 24, 2015 at 6:16 PM, Radar Da lei <rl...@pivotal.io> wrote:
> Hi Roman,
>
> I plan to build out an Apache HAWQ binary tarball for users to download, so
> they can install HAWQ easier.
>
> But this will require we include all the third party libraries in the
> tarball(currently we requires user to manually install them on each node),
> I'm not quite sure if this action have license or other issues.
>
> Would you please give some advice? Thanks a lot.

I see you guys publishing two types of binary tarballs:
   1. Nightly builds
   2. Convenience binary associated with particular release of HAWQ

In both cases it is extremely important to make sure you're
not bundling any Cat X licensed binaries into the tarball
(most of the time this means GPL). As long as you don't
you should make sure that:
    1. Nightly builds are NOT advertised outside of your
    developer community. E.g. you can't link to them on
    the Download page of the HAWQ's website, etc.

    2. Convenience binary tarball is included in the formal
    release vote.

These are the basic rules. If you can give me a link to
a tarball available on Jenkins I can give you more feedback
on the content.

Hope this helps.

Thanks,
Roman.