Created a PR for eleveldb develop branch : 

https://github.com/basho/eleveldb/pull/254 
<https://github.com/basho/eleveldb/pull/254>

Lets operate on the basis that :

The future of Riak is leveled - particularly as there's been next to no 
maintenance on this since 2016
The develop branch is for users of rebar3, that's a reasonable presumption in 
2019
People would like to be able to build on OSX, Alpine, Debian.
People are using riak_core and it needs hashtree/metadata etc which are all 
dependent upon eleveldb (for now).
People are using Erlang 20+, and in many cases Erlang 22
People are using riak_core in Elixir applications
Lots of people do their daily work on OSX.
This PR :

Removes the usage of rebar (the binary blob that you don't really know where it 
came from or what it does).
Provides two dockerfiles, one for Alpine, one for debian that demonstrate 
what's necessary to get eleveldb to build on those two platforms, using rebar3, 
with these changes - perhaps those docker builds could be added to travis (if 
it's still running) in a future PR.
Uses the operating system provided version of snappy instead of using an 
arbitrary, unverified (no checksum) version of the snappy library marked as 
1.0.4 - incidentally, there is an existing security advisory for snappy version 
1.1.4. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7577 
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7577> - in any event 
the intention was to switch to lz4 as the default - I think we can agree this 
doesn't represent very good practice now (made sense at the time).
Downside :
The tools for inspecting SST files don't build - can't get them to work in any 
of the envs (OSX,Alpine,Debian) - perhaps someone with better c/c++ experience 
can figure that out - in any event nobody uses them apart from @matthewvon 
<https://github.com/matthewvon> - maybe he can offer a suggestion/tweak to get 
them working again. I think that's acceptable for now.




-- 


Code Sync & Erlang Solutions Conferences

Code BEAM Lite BD 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66scls> - Budapest: 
20 September 2019

Code BEAM Lite NYC 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66scvd> - NYC: 01 
October 2019

Code BEAM Lite 
<https://codesync.global/conferences/code-beam-lite-berlin-2019/> - Berlin: 
11 October 2019

RabbitMQ Summit 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66sd8l> - London: 4 
November 2019

Code Mesh LDN 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66sd8x> - London: 7-8 
November 2019

Code BEAM Lite India 
<https://codesync.global/conferences/code-beam-lite-bangalore/> - 
Bangalore: 14 November 2019

Code BEAM Lite AMS 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66sdbs> - Amsterdam: 
28 November 2019

Lambda Days 
<https://www2.erlang-solutions.com/l/23452/2019-06-24/66sdcd> - Kraków: 
13-14 February 2020

Code BEAM SF - San Francisco: 5-6 March 2020





*Erlang Solutions cares about your data and privacy; please find all 
details about the basis for communicating with you and the way we process 
your data in our **Privacy Policy* 
<https://www.erlang-solutions.com/privacy-policy.html>*.You can update your 
email preferences or opt-out from receiving Marketing emails here 
<http://www2.erlang-solutions.com/emailpreference>.*
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to