> On 14 Mar 2018, at 12:46, Dmitry Pavlov <dpavlov....@gmail.com> wrote:
>
> Hi,
>
> Did not understand fully that splitted delivery means.
> Is it correct,that user will have install
> install ignite:core
> install ignite:opt_libs
> with separated commands?
It will be one command with several arguments, i.e.
yum install ignite-core ignite-optional
Also, I considered splitting optional libs per package (like php / perl / etc.
do, for example) but not sure whether these efforts are appropriate at this
moment.
I guess this scheme must have huge support from the community.
>
> Or there will be some aggregating package like ignite:full and several
> options like ignite:core.
Nice idea! If community will agree, I can add aggregating virtual package with
dependencies on all other for corresponding release. It can even keep current
name ‘apache-ignite’ :)
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 14 мар. 2018 г. в 12:36, vveider <mr.wei...@gmail.com>:
>
>> Hi, Igniters!
>>
>>
>> Release 2.4 is almost there, at least binary part of it, so I'd like to
>> move
>> forward to further improve and widen AI delivery through packages.
>> As of now, Apache Ignite ships in RPM package weighing about 280M+ and, to
>> improve usability and significantly reduce required download sizes, I
>> purpose that in 2.5 release we introduce splitted delivery as follows:
>> - CORE
>> - bin
>> - config
>> - libs (!optional)
>> - OPTIONAL LIBS
>> - BENCHMARKS
>> - DOCS (?)
>> - EXAMPLES
>> - .NET PLATFORM FILES
>> - C++ PLATFORM FILES
>>
>> This architecture, as I assume, will add flexibility (no reason to download
>> all 280M+ of binaries where you are to run only core node functionality)
>> and
>> maintainability (you are in full control of what is installed on your
>> system).
>>
>> After successful architecture choice, same scheme are planned to be used in
>> DEB packages as well.
>>
>> WDYT?
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>
