File /usr/local/bin/gpgconf.ctl missing and mostly undocumented

[Dennis Clarke]

The struggle continues to get gnupg to "just work". By running a trace 
on the command "gpgconf --check-programs" I see this :


access("/usr/local/bin/gpgconf.ctl", F_OK) = -1 ENOENT (No such file or 
directory)

In the sources I see the file doc/gnupg.info-2 which has a section
10.4.9 talking about "Files used by gpgconf". There is no such file
and no example of what it would even look like.  I did find that file
mentioned in the sources common/homedir.c and no other C source.

The first mention of this new file is :


2021-09-17  Werner Koch  <wk at gnupg.org>

         common: Support a gpgconf.ctl file under Unix.
         + commit d4768bb982adb5c8410303334ee8d82ba0d71f3b
         * common/homedir.c (unix_rootdir): New.
         (gnupg_bindir): Use it.
         (gnupg_libexecdir): Use it.
         (gnupg_libdir): Use it.
         (gnupg_datadir): Use it.
         (gnupg_localedir): Use it.

         common: New function substitute_envvars.
         + commit 9c272dc245456d5403e3bd50553b4fdccb370e27
         * common/stringhelp.c (substitute_envvars): New.  Based on code in
         gpg-connect-agent.
         * common/t-stringhelp.c: Include sysutils.h.
         (test_substitute_envvars): New.

With various things being done all the way up until December last year :

2023-12-22  Werner Koch  <wk at gnupg.org>

         common: Add keyword socketdir to gpgconf.ctl.
         + commit 239c1fdc28dcd0dc7aa5341be7c966da2231642a
         * common/homedir.c (enum wantdir_values): New enums.
         (unix_rootdir): Change arg to use the enums.  Adjust all 
callers.  Add
         support for the socketdir keyword.
         (_gnupg_socketdir_internal): Take care of the socketdir keyword in
         gpgconf.ctl.

         * doc/tools.texi (Files used by gpgconf): Briefly explain the
         gpgconf.ctl syntax.


So it looks to be a pretty important file to have.

Except there is little or no documentation about it other than the sources.

So then ... can this file be hacked into place somehow or was it
supposed to have been installed by default at "make install" or some
other deep magic?


-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken