Implications of a common private keys directory in 2.1

[Carola Grunwald]

On Sun, 16 Oct 2016 01:22:50 +0000 (UTC), I wrote:

>Hi,
>
>my next problem with 2.1.15 on Windows 7.
>
>I add a pub/sec keypair to two different keyrings
>  '--import ... --keyring a.kbx', then '--import ... --keyring b.kbx'.
>Following this I delete that key from one of the keyrings
>  '--delete-secret-and-public-key ... --keyring a.kbx',
>which unfortunately as a side effect also removes the secret key
>associated with the other public keyring (b.kbx), as for both public key
>items there's only one single secret key file stored in the common
>private-keys-v1.d directory.
>
>Is there any chance to get that disentangled, maybe by defining a
>separate secret key directory for each public .kbx keyring in use?

The silence makes me believe that what I described is intended behavior,
not a 2.1 design flaw. I'd like to know whether that's correct. Any
response would still be appreciated.

Kind regards,

Caro