Change Details

When attempting to use a custom GPGHOME (specifically trying, without success, to get gnupg to respect XDG_CONFIG_HOME/gnupg), I discovered both: ``` export GNUPGHOME=[ anything ] gpgconf --list-dirs --dry-run ``` Will always create the weirdly hashed socket dir in XDG_RUNTIME_DIR/gnupg. I expect --create-socketdir to create the directory, I don't expect but at least somewhat understand --list-dirs doing it, but with the --dry-run flag there definitely should not be a directory created.

When attempting to use a custom GPGHOME (specifically trying, without success, to get gnupg to respect XDG_CONFIG_HOME/gnupg), I discovered that the following: ``` export GNUPGHOME=[ anything ] gpgconf --list-dirs --dry-run ``` ... will always create the weirdly hashed socket dir in XDG_RUNTIME_DIR/gnupg. I expect --create-socketdir to create the directory, I don't expect but at least somewhat understand --list-dirs doing it, but with the --dry-run flag there definitely should not be a directory created.

When attempting to use a custom GPGHOME (specifically trying, without success, to get gnupg to respect XDG_CONFIG_HOME/gnupg), I discovered both:that the following: ``` export GNUPGHOME=[ anything ] gpgconf --list-dirs --dry-run ``` Will... will always create the weirdly hashed socket dir in XDG_RUNTIME_DIR/gnupg. I expect --create-socketdir to create the directory, I don't expect but at least somewhat understand --list-dirs doing it, but with the --dry-run flag there definitely should not be a directory created.