[MacPorts] #63708: kibana: evaluate feasibility of building from upstream source

[MacPorts]

#63708: kibana: evaluate feasibility of building from upstream source
-------------------------+----------------------
 Reporter:  mascguy      |      Owner:  mascguy
     Type:  enhancement  |     Status:  assigned
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:  2.7.1
 Keywords:               |       Port:  kibana
-------------------------+----------------------
 Presently, `kibana` utilizes upstream's published binaries, due to various
 technical challenges related to building.

 The details are as follows, taken from a brief commit-related discussion
 between Steve Smith and myself:

 >> Longer-term, it would definitely be preferable to build from source.
 Have you taken a look at what's involved? (Not an emergency though.)
 >
 > I tried that at first, but it's tough and now involves bazel, so I just
 threw in the towel and downloaded the build that Elastic provides.
 >
 > In addition to the necessity of figuring out the bazel build, it's not
 clear to me how stable their build process is right now, and I perceive a
 possible risk of a lot of maintenance to keep up as that process evolves.
 I don't have any special insight though.
 >
 > See: https://lists.macports.org/pipermail/macports-
 dev/2021-September/043697.html

 One key challenge, per the linked mailing list discussion, relates to
 conflicting inter-dependencies of the various Node/NPM ports. So that is
 very much a critical path for this work; tracked by issue:63035.

 Once the latter has been tackled, this should be more feasible. But with
 the caveat mentioned by Steve, which is that upstream may be a moving
 target.

 We'll have a better idea once the Node/NPM conflicts have been addressed,
 over the next few months. And perhaps upstream's build process may be more
 stable by then. Still TBD though.

-- 
Ticket URL: <https://trac.macports.org/ticket/63708>
MacPorts <https://www.macports.org/>
Ports system for macOS