Thanks for the background Radar and Lei. FYI: it does appear both libhdfs3 and libyarn both depended on gsasl for build and runtime support. Here is the "otool" output from macOS which shows this runtime dependency:
libhdfs3.1.dylib: libhdfs3.1.dylib (compatibility version 1.0.0, current version 2.2.31) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.60.2) /usr/local/opt/protobuf/lib/libprotobuf.13.dylib (compatibility version 14.0.0, current version 14.2.0) /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.9.0) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0) /usr/local/opt/gsasl/lib/libgsasl.7.dylib (compatibility version 17.0.0, current version 17.6.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.5.0) libyarn.0.1.17.dylib: libyarn.1.dylib (compatibility version 1.0.0, current version 0.1.17) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.60.2) /usr/local/opt/protobuf/lib/libprotobuf.13.dylib (compatibility version 14.0.0, current version 14.2.0) /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.9.0) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0) /usr/local/opt/gsasl/lib/libgsasl.7.dylib (compatibility version 17.0.0, current version 17.6.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.5.0) On Fri, Jul 7, 2017 at 8:05 AM, Lei Chang <[email protected]> wrote: > > Radar is correct. when we open sourced HAWQ, GPL/LGPL runtime/build > dependencies have been considered. > > Cheers > Lei > > > > > On Fri, Jul 7, 2017 at 1:54 PM, Radar Lei <[email protected]> wrote: > >> Hi Ed, >> >> Per my understanding, libgsasl is a build and runtime dependence of HAWQ, >> but it's not included in HAWQ source code and HAWQ binary release tarball. >> >> If you check the HAWQ rpm dependences, you can see 'libgsasl' is listed in >> 'hawq.spec', user need to install it before install HAWQ. >> >> So I think we don't need care if it's Apache License compatible and don't >> need to include it in our license file. Thanks. >> >> >> >> Regards, >> Radar >> >> On Fri, Jul 7, 2017 at 1:34 PM, Ed Espino <[email protected]> wrote: >> >> > HAWQ Dev, >> > >> > I have been filling out the project's Apache Project Maturity Model at >> the >> > following location: >> > https://cwiki.apache.org/confluence/display/HAWQ/ >> > Apache+Project+Maturity+Model >> > >> > In trying to gather information for the Licenses and Copyright section >> > (specifically: LC20 and LC30), I started to review dependent third party >> > components. I reviewed the project's LICENSE file ( >> > https://github.com/apache/incubator-hawq/blob/master/LICENSE). In >> > addition, >> > I reviewed the build and install steps from the wiki. I noticed one >> > component (libgsasl 1.8.0) which is listed but isn't listed in the >> LICENSE >> > file. This component is a build dependency of the libhdfs3 component ( >> > https://github.com/apache/incubator-hawq/blob/master/ >> > depends/libhdfs3/README.md). >> > The component libhdfs3 will not build without the development >> > libgsasl (header and libs) available. The component libgsasl is the GNU >> > SASL Library (https://www.gnu.org/software/gsasl/). >> > >> > Here is it's licensing information: >> > >> > The core GNU SASL library, and most mechanisms, are licensed under the >> GNU >> > Lesser General Public version 2.1 (or later). It is distributed >> separately, >> > as the "libgsasl" package. The GNU SASL command line application, self >> test >> > suite and more are licensed under the GNU General Public License >> version 3 >> > (or later). The "gsasl" package distribution includes the library part >> as >> > well, so you do not need to install two packages. >> > >> > To the best of my knowledge, this dependent component libgsasl is not >> > compatible with Apache Software projects. Have there been any >> discussions >> > in the past on its use in HAWQ? I couldn't find any in the mail >> archives. I >> > could be entirely wrong and this could be a false alarm. If anyone can >> > provide some information, it would be greatly appreciated. >> > >> > Regards, >> > -=e >> > >> > -- >> > *Ed Espino* >> > >> > > -- *Ed Espino*
