[issue114] gpgme_key_t should include the gpgme_key_list_mode_t in force when creating it

New submission from Marc Mutz <[email protected]>:

This is because some bits in gpgme_key_t change their meaning, depending on the 
flags used in the keylisting they originate from: 
 
E.g. !revoked means "is not revoked revoked" only if the VALIDATE flags was 
used, otherwise it has no meaning (or, more precisely, is undefined). 
 
Or uids->signatures == NULL means something different whether or not the 
keylisting included signatures. 
 
I've implemented it for gpgme++ myself, but of course it should be in gpgme 
itself.

----------
assignedto: marcus
messages: 503
nosy: marc, marcus
priority: feature
status: unread
title: gpgme_key_t should include the gpgme_key_list_mode_t in force when creating it
topic: GPGME
______________________________________________________
Aegypten issue tracker <[email protected]>
<https://intevation.de/roundup/aegypten/issue114>
______________________________________________________