[MacPorts] #61310: notmuch @0.31 +emacs: variable rsti_dir is empty

[MacPorts]

#61310: notmuch @0.31 +emacs: variable rsti_dir is empty
----------------------+-----------------------
  Reporter:  lafpark  |      Owner:  rseichter
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.6.3
Resolution:           |   Keywords:
      Port:  notmuch  |
----------------------+-----------------------
Changes (by ryandesign):

 * cc: ryandesign (added)


Comment:

 Replying to [comment:12 lafpark]:
 > My realpath behaves differently, if that helps.

 Where is your `realpath`?

 {{{
 which realpath
 }}}

 What version is it?

 {{{
 realpath -v
 port provides $(which realpath)
 }}}

 (I'm aware that MacPorts realpath 1.0.1 claims to be 1.0.0; see #61330.)


 Replying to [comment:14 rseichter]:
 > If your version of realpath is broken in some way, there's nothing I can
 do about it. It should never return an empty string, but always a path (or
 an error). The notmuch port works on my machines and on the MacPorts build
 infrastructure, so I have little choice but to close this issue as non-
 reproducible.

 On MacPorts build infrastructure,
 [https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/37864/steps
 /install-port/logs/stdio you'll see] that the configure script printed
 this warning:

 {{{
 ./configure: line 1539: realpath: command not found
 }}}

 Since it seems evident that notmuch needs realpath at configure time, the
 port should add `port:realpath` to its `depends_build`. This will ensure*
 that MacPorts realpath, which behaves the way you expect, will be used,
 rather than whatever other realpath the user somehow has.

 (* except if the user removes /opt/local/bin from binpath in
 macports.conf)

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