Not a bundling but creating a compat packages for older version where needed. Nothing stops people from creating them now. Alexander Kurtakov Red Hat Eclipse team ----- Original Message ----- > From: "Josh Boyer" <jwboyer@xxxxxxxxxxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Wednesday, December 17, 2014 4:25:35 PM > Subject: Re: F22 System Wide Change: Elasticsearch > > On Wed, Dec 17, 2014 at 9:03 AM, Jaroslav Reznik <jreznik@xxxxxxxxxx> wrote: > > = Proposed System Wide Change: Elasticsearch = > > https://fedoraproject.org/wiki/Changes/Elasticsearch > > > > Change owner(s): Jiri Vanek <jvanek@xxxxxxxxx> > > > > Goal of this change is to pack Elasticsearch into main Fedora repo. > > > > == Detailed Description == > > The Elasticsearch [1] is fully-featured self-standing opensource [2] > > indexing > > server. Many people and many tools do use it. And many people do want it in > > Fedora. Aim of this Change is to make elastic search available by simple > > yum > > install elasticsearch, and of course enable it as dependence. To build a > > custom indexing tool on top of elastic search is more easy than current > > upstream install and download. > > > > == Scope == > > * Proposal owners: > > ** pack Elasticsearch - nearly done - see RHBZ#902086 > > ** make it somehow works > > ** verify it works > > ** tune list of crucial dependencies > > ** enable Elasticsearch as service - something what have to be decided > > > > * Other developers: > > ** '''This is crucial part of this proposal''' > > ** Elastic search is extremely tuned application, and like it, its > > dependencies must be strictly kept in correct versions > > ** Currently known troublemakers: > > *** lucene > > *** netty3 > > *** sigar > > *** compress-lzf > > *** guava (currently needed 18, avaiable 17) > > So from what I can tell, the dependency issues are the only thing that > is preventing this from being a self-contained Change. Is that > correct? > > If so, perhaps pursuing a bundling exception would be a more > straightforward approach. > > josh > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
