Hi All, The same situation is for Go lang also. There are no binaries. Libraries are installed from source code repo, etc.:
go get -u github.com/amsokol/ignite-go-client So the proposal is not really applicable to Go lang client. Thanks, Aleksandr From: Pavel Petroshenko Sent: 16 июня 2018 г. 21:10 To: Denis Magda Cc: dev Subject: Re: Separate binaries for thin clients and drivers Hi Denis, There are no "binaries" for Node.js and Python that you can download. These Thin Clients are distributed and installed by a package management system (npm, pip): which resolves all the dependencies and deploys necessary components to the appropriate system locations. So instead of downloading a Node or Python package binary, the package management systems should be used to properly install it: Node.js: $ npm install <...> or Python: $ pip install <...> So the proposal is not really applicable to these clients. Pavel On Sat, Jun 16, 2018 at 12:45 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > +1 > > On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda <dma...@apache.org> wrote: > > > Igniters, > > > > Presently, all our thin clients and SQL drivers are stored in the main > > Ignite repository. That's totally fine, I wouldn't change anything in > here. > > > > But, what I would encourage us to contemplate on is how a user gets and > > downloads those binaries. Basically, the user has to download the whole > > Ignite distribution even if he needs just a JDBC driver or Node.JS thin > > driver. > > > > The proposal is pretty simple. In addition to the main distribution, > let's > > prepare separate ZIP archives with binaries for: > > > > - JDBC > > - ODBC > > - Thin clients (Java, C#, Node.JS, Python, etc.) > > > > The binaries would be available for downloads on the main page: > > https://ignite.apache.org/download.cgi > > > > Thoughts? Supporters and opposers, please speak out. > > > > -- > > Denis > > >
