Date: Thu, 30 Mar 2017 18:27:18 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: "Bradley T. Hughes" <bradleythughes@fastmail.fm> Cc: "ports@FreeBSD.org" <ports@FreeBSD.org>, tj@FreeBSD.org Subject: Re: textproc/kibana50 and version of node.js Message-ID: <58DD31E6.7010303@quip.cz> In-Reply-To: <B7C932F5-4320-4C65-88A2-E79B33490F7F@fastmail.fm> References: <58DCBB1B.7090507@quip.cz> <B7C932F5-4320-4C65-88A2-E79B33490F7F@fastmail.fm>
next in thread | previous in thread | raw e-mail | index | archive | help
Bradley T. Hughes wrote on 2017/03/30 11:10: > >> On 30 Mar 2017, at 10:00, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> Hi, > > Hi! :) > >> we are using npm + node in version 7.8.0 and ElasticSearch in version 5.0.2. Now we need Kibana and Kibana X-Pack but official Kibana has bundled node v0.10 or v0.12, FreeBSD port of Kibana has dependency on node v4. It is conflicting with already installed and used node v7. > > This mail caught my eye. Since Node.js v0.10 and v0.12 have reached end-of-life, I wanted to see if I could find out why they were bundling such an old version. Looking at Github, it actually looks like Kibana is bundled with Node.js v6.9.5: https://github.com/elastic/kibana/blob/v5.3.0/package.json#L243-L246 I am sorry, it was my fault. It was information for older version of Kibana (4.4.1, 4.3.2, 4.1.5) https://discuss.elastic.co/t/kibana-4-4-1-4-3-2-4-1-5-updated-node-js-versions-due-to-upstream-vulnerabilities/41643 I created Kibana 5.0.2 package with poudriere with modified Makefile to: RUN_DEPENDS= node>=0.8.0:www/node Kibana is up and running with Node.js 7.8. I hope it will be stable :) Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58DD31E6.7010303>