kibana submission node version conflict issue

[Blair Zajac]

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.
> 
>> On Sep 2, 2021, at 10:26, Blair Zajac <blair at orcaware.com> wrote:
>> 
>> Is nodejs10 really needed? A newer nodejs won’t work?
>> 
>> Blair
>> 
>>> On Sep 2, 2021, at 3:12 AM, Steven Smith <steve.t.smith at gmail.com <mailto:steve.t.smith at gmail.com>> wrote:
>>> 
>>> I submitted a PR for Kibana: https://github.com/macports/macports-ports/pull/12055 <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, I use:
>>> 
>>>> depends_build-append	yarn
>>>> depends_lib-append	path:bin/node:nodejs10
>>> 
>>> 
>>> But yarn has the run dependency on nodejs16:
>>> 
>>>> depends_run-append	path:bin/node:nodejs16
>>> 
>>> The install command tries to install both nodejs10 and nodejs16, which conflict, and the CI fails.
>>> 
>>> This can be fixed by hand by deactivating nodejs16, but we need the CI and buildbot to work automatically.
>>> 
>>> How can this node version conflict be resolved?
>>> 
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210902/2a6ba713/attachment.htm>