Package: lbdb
Version: 0.42

There is a hard-coded path segment in `lbdb-munge.sh.in` which is
currently causing problems on macOS in the Homebrew-installed
version of lbdb, but I believe that it can affect all platforms:

    prefix=@prefix@
    exec_prefix=@exec_prefix@
    dotlock=@DOTLOCK@
    fetchaddr=@libdir@/fetchaddr
    db=$HOME/.lbdb/m_inmail.utf-8
    munge="${prefix}/lib/lbdb/munge"

Specifically, if you pass `--libdir` to the `configure` script,
then the "munge" script will get installed in that location, but
the last line above expects it to exist under
"@prefix@/lib/lbdb/munge", which will only work if `--libdir`
happens to equal "@prefix@/lib/libdb". It does not in the case of
the Homebrew formula. I've submitted a pull request to ameliorate
the breakage by not supplying a custom `--libdir`, but I don't
know whether it will be accepted there:

https://github.com/Homebrew/homebrew-core/pull/7759

It seems the fix here should be something like changing that last
line to:

    munge=@libdir@/munge

I am not sure if any other places in the lbdb package exhibit the
same problem.

Thanks for looking in to this (and I hope I've reported this via
the right channel!).

Reply via email to