kibana submission node version conflict issue
steve.t.smith at gmail.com
Fri Sep 3 00:14:32 UTC 2021
> 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 <blair at orcaware.com> wrote:
> 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 <steve.t.smith at gmail.com> wrote:
>> 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 <blair at orcaware.com> wrote:
>>> Newer kibana? Nodejs16 doesn’t need bazel...
>>>> On Sep 2, 2021, at 1:41 PM, Steven Smith <steve.t.smith at gmail.com> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev