[MacPorts] #48937: New port: Bazel

[MacPorts]

#48937: New port: Bazel
-------------------------+--------------------------------
  Reporter:  ahh         |      Owner:  macports-tickets@…
      Type:  submission  |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  bazel       |
-------------------------+--------------------------------

Comment (by RootFunction):

 I'm not really aware of any big reasons why compiling from source would be
 better than running the installer, so I went with the installer method
 because it was somewhat easier. Perhaps it would be slightly more prudent
 to compile from source in order to ensure that the binary runs on the
 user's machine, so for that reason I wouldn't mind changing approaches.
 The source code archive is also just over half the size of the installer
 script, so compiling from source makes sense if you also want to save
 bandwidth.

 I agree with the suggestion of adding a dependency on Java. Could we not
 just add a check for JDK 8 or greater without worrying about which of its
 Java libraries are actually being used? On OSX, Bazel requires JDK 8 and
 the Xcode command line tools - assuming you're not using Homebrew.
 MacPorts already requires the Xcode command line tools. If there are
 particular Java runtime + OS X version combinations that don't work when
 installing the port with MacPorts, then wouldn't it be the case that those
 combinations would also fail when installing the port manually? I think in
 these situations, the correct course of action would be to file tickets
 with the port developers.

--
Ticket URL: <https://trac.macports.org/ticket/48937#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS