[MacPorts] #48937: New port: Bazel

MacPorts noreply at macports.org
Fri May 12 10:35:37 UTC 2017


#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 raimue):

 I propose the following changes:

 * What is the reason for deleting `${distpath}` in post-destroot? Users
 are supposed to use `port clean --dist` or `port reclaim` to get rid of
 distfiles. I removed that command.

 * `${worksrcdir}` is not supposed to be empty. Extracted files would be
 dumped directly into `${workpath}` which might lead to name clashes (e.g.
 names like destroot, .home, .tmp, etc. are in use). Use `extract.mkdir` to
 create the subdirectory before extracting.

 * What exactly do you want to achieve with that `sudo sh` in `build {}`?
 The build phase is supposed to run as the "macports" user without super
 user privileges. I do not understand why stderr is a problem, but
 shouldn't the output be redirected (as in `2>&1`) instead of being ignored
 completely?

 Additionally, the part on getting the compiler version of javac would
 probably be better suited for the java port group. I'll leave that to
 people with more knowledge about Java on macOS.

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


More information about the macports-tickets mailing list