[PATCH 7/9] add a gpg_path value for notmuch_database_t

Daniel Kahn Gillmor dkg at fifthhorseman.net
Fri Dec 11 20:10:19 PST 2015


On Fri 2015-12-11 17:35:58 -0500, J. Lewis Muir wrote:
> I guess I still don't get it.  Why even have a _find_in_path function?
> Why not just expect the gpg executable path to have already been
> specified somehow (e.g. Notmuch configuration file, build-time constant,
> or environment variable)?

This is happening in the library, which doesn't read the config file,
and doesn't depend on the environment.  if a user tells the library "use
this as your gpg executable", it seems nice to fail early for them.

It's also nice if we want to have a default that says something like
"use gpg2 if it's available, but gpg otherwise".

     --dkg


More information about the notmuch mailing list