David Shaw <[EMAIL PROTECTED]>: > On Wed, Nov 29, 2006 at 12:24:48AM +0200, Markus Järvinen wrote: > > Package: gnupg > > Version: 1.4.5-2 > > Severity: normal > > > > If I understand correctly, "gpg --no-options" is supposed to ignore > > ~/.gnupg completely. However I get the following errors when using it: > > > > $ echo foo | gpg -c --no-options >/dev/null > > gpg: keyblock resource `/home/m/.gnupg/pubring.gpg': file open error > > gpg: can't create `/home/m/.gnupg/random_seed': No such file or directory > > $ echo $? > > 2 > > No, --no-options just ignores the gpg.conf file. Other things in > ~/.gnupg (keyrings, random_seed), are still used. Also, if you don't > have a ~/.gnupg, --no-options prevents automatically creating one > (which may be what happened in the example above).
Yes, that's what happened and now when I think about it the behavior is as documented. But what's the reasoning for not creating ~/.gnupg if it's still needed?
