Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPYoqXQX-pFzwd+W1rocn32q9iuoc2gcjCHX=H3rhYDwTx+4Tg@mail.gmail.com>
References: <CAPYoqXQX-pFzwd+W1rocn32q9iuoc2gcjCHX=H3rhYDwTx+4Tg@mail.gmail.com>
From: Joe Witt <joe.witt@gmail.com>
Date: Wed, 19 Jul 2017 14:04:06 -0400
Message-ID: <CALJK9a6R0JpFXuJG2h2=rFHAoeXPko_cD6guD9ijzqk-9+RfHQ@mail.gmail.com>
Subject: Re: Binaries in embedded redis jar files
To: dev@nifi.apache.org
Content-Type: text/plain; charset="UTF-8"
archived-at: Wed, 19 Jul 2017 18:04:12 -0000

It is not a problem.  It would be an issue if those were part of our
source release which is the official apache release artifact.


On Wed, Jul 19, 2017 at 1:58 PM, Joe Skora <jskora@apache.org> wrote:
> I noticed a new jar dependency for Redis includes binaries.
>
> $ jar -xf
>> ~/.m2/repository/com/github/kstyrc/embedded-redis/0.6/embedded-redis-0.6.jar
>> $ ls -l
>> total 6292
>> drwxr-xr-x. 3 user1 users      36 Apr 12  2015 META-INF/
>> drwxr-xr-x. 3 user1 users      21 Apr 12  2015 redis/
>> -rw-r--r--. 1 user1 users 4236300 Apr 12  2015 redis-server-2.8.19
>> -rw-r--r--. 1 user1 users  806944 Apr 12  2015 redis-server-2.8.19.app
>> -rw-r--r--. 1 user1 users 1392640 Apr 12  2015 redis-server-2.8.19.exe
>> $ file redis-server*
>> redis-server-2.8.19:     ELF 64-bit LSB executable, x86-64, version 1
>> (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24,
>> BuildID[sha1]=c59ab61e1d5b94e26d079b04e9e593b6be3f0230, not stripped
>> redis-server-2.8.19.app: Mach-O 64-bit executable
>> redis-server-2.8.19.exe: PE32+ executable (console) x86-64, for MS Windows
>>
>
> So, installing NiFi will include externally built binaries, not just
> scripts but full ELF, MacOS, and Windows PE binaries.
>
> Is this a problem for Apache?  Does this cause concern for anyone else?
>
> Regards,
> Joe