RE: kibana submission node version conflict issue

2021-10-02 Thread Christopher Nielsen
> On Oct 2 2021, at 05:30, Ryan Schmidt wrote: > >> On Sep 2, 2021, at 05:12, Steven Smith wrote: >> >> How can this node version conflict be resolved? > > The node ports should be fixed so that they do not conflict with one another. Agreed, and tracked by open issue: https://trac.macports.org

Re: kibana submission node version conflict issue

2021-10-02 Thread Ryan Schmidt
On Sep 2, 2021, at 05:12, Steven Smith wrote: > How can this node version conflict be resolved? The node ports should be fixed so that they do not conflict with one another.

Re: kibana submission node version conflict issue

2021-09-10 Thread Steven Smith
I’ve updated this submission with a working Portfile that uses the elastic build, just like the elasticsearch port. > On Sep 2, 2021, at 20:14, Steven Smith wrote: > >  >> Why not use bazel? > > > Because bazel a major PITA, doesn’t work well or at all behind firewalls, and > if there are b

Re: kibana submission node version conflict issue

2021-09-02 Thread Steven Smith
> Why not use bazel? Because bazel a major PITA, doesn’t work well or at all behind firewalls, and if there are bazel kibana build instructions, I don’t see them. > On Sep 2, 2021, at 17:40, Blair Zajac wrote: > > Well, we have bazel already and TensorFlow uses it to build. Why not use > ba

Re: kibana submission node version conflict issue

2021-09-02 Thread Blair Zajac
Well, we have bazel already and TensorFlow uses it to build. Why not use bazel? > On Sep 2, 2021, at 2:32 PM, Steven Smith wrote: > > Newer versions of kibana need bazel to build: > https://github.com/elastic/kibana/blob/7.14/package.json >

Re: kibana submission node version conflict issue

2021-09-02 Thread Steven Smith
Newer versions of kibana need bazel to build: https://github.com/elastic/kibana/blob/7.14/package.json > On Sep 2, 2021, at 16:54, Blair Zajac wrote: > > Newer kibana? Nodejs16 doesn’t need bazel... > >> On Sep 2, 2021, at 1:41 PM, Steven Smith wrote: >> >> The newer ones need (ugh) bazel t

Re: kibana submission node version conflict issue

2021-09-02 Thread Blair Zajac
Newer kibana? Nodejs16 doesn’t need bazel... > On Sep 2, 2021, at 1:41 PM, Steven Smith wrote: > > The newer ones need (ugh) bazel to build. > > I’m thinking of just throwing in the towel and just using the pre-“built” > download. > >> On Sep 2, 2021, at 10:26, Blair Zajac wrote: >> >> Is

Re: kibana submission node version conflict issue

2021-09-02 Thread Steven Smith
The newer ones need (ugh) bazel to build. I’m thinking of just throwing in the towel and just using the pre-“built” download. > On Sep 2, 2021, at 10:26, Blair Zajac wrote: > > Is nodejs10 really needed? A newer nodejs won’t work? > > Blair > >> On Sep 2, 2021, at 3:12 AM, Steven Smith wro

Re: kibana submission node version conflict issue

2021-09-02 Thread Blair Zajac
Is nodejs10 really needed? A newer nodejs won’t work? Blair > On Sep 2, 2021, at 3:12 AM, Steven Smith wrote: > > I submitted a PR for Kibana: > https://github.com/macports/macports-ports/pull/12055 > > > The CI fails because of an issu

kibana submission node version conflict issue

2021-09-02 Thread Steven Smith
I submitted a PR for Kibana: https://github.com/macports/macports-ports/pull/12055 The CI fails because of an issue with a conflicting dependency on the node version. kibana needs nodejs10 to build and run, and yarn to build; therefore,