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

[Werner Koch]

Hi!

On Sat, 20 Jul 2024 06:54, Dennis Clarke said:
> 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)

That checks whether this _optional_ file exists.


From the man page:

  gpgconf.ctl
         Under Unix ‘gpgconf.ctl’ may be used to change some of the
         compiled in directories where the GnuPG components are expected.  This
         file is expected in the same directory as ‘gpgconf’.  The
         physical installation directories are evaluated and no symlinks.
         Blank lines and lines starting with pound sign are ignored in the
         file.  The keywords must be followed by optional white space, an equal
         sign, optional white space, and the value.  Environment variables are
         substituted in standard shell manner, the final value must start with
         a slash, trailing slashes are stripped.  Valid keywords are
         rootdir, sysconfdir, socketdir, and
         .enable.  No errors are printed for unknown keywords.  The
         .enable keyword is special: if the keyword is used and its
         value evaluates to true the entire file is ignored.

         Under Windows this file is used to install GnuPG as a portable
         application.  An empty file named ‘gpgconf.ctl’ is expected in
         the same directory as the tool ‘gpgconf.exe’ or the file must
         have a keyword portable with the value true.  The root of the
         installation is then that directory; or, if ‘gpgconf.exe’ has
         been installed directly below a directory named ‘bin’, its parent
         directory.  You also need to make sure that the following directories
         exist and are writable: ‘ROOT/home’ for the GnuPG home and
         ‘ROOT/usr/local/var/cache/gnupg’ for internal cache files.

         On both platforms the keyword gnupg can be used to change the
         standard home directory.  For example a value of "gnupg-vsd" will
         change the default home directory on unix from ‘~/.gnupg’ to
         ‘~/.gnupg-vsd’.  The socket directory is changed accordingly
         unless the socketdir keyword has been used.  On Windows the
         Registry keys are modified as well.



Salam-Shalom,

   Werner


-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20240723/737bcd49/attachment.sig>