[dput-ng-maint] Bug#714318: dcut: a way to set the default keyid would be nice

[Russ Allbery]

Package: dput-ng
Version: 1.4
Severity: wishlist

Like, I suspect, a lot of people, I have two keys with identical
key IDs, one of which is a 1024-bit RSA key that I no longer use.
Since I created it first, it's earlier in GnuPG's keyring, so key
selection by name and email address will generally always choose it.

Most Debian infrastructure commands have a way of persistently
configuring the actual key ID to use instead so that I can point
them at my newer key.  dcut takes the -k option, which works fine,
but there doesn't seem to be a way to persistently configure it with
either an environment variable or a configuration file.

I can just create a shell alias of dcut to dcut -k <keyid>, but it
would be nice if there were some place I could stick that in a
configuration file.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.8-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dput-ng depends on:
ii  python       2.7.5-2
ii  python-dput  1.4

Versions of packages dput-ng recommends:
ii  bash-completion  1:2.0-1

dput-ng suggests no packages.

-- no debconf information