* ABI's to break:
** I/O and User Data could be made extensible. But this can be done
without breaking the ABI hopefully.
-** gpgme_keylist_mode_t should not be an enum. Maybe some other values
- should also not be an enum. All enums that should be enums need to
- have a maximum value to ensure a certain minimum width for
- extensibility.
+* All enums that should be enums need to have a maximum value to ensure a certain minimum width for extensibility.
** Compatibility interfaces that can be removed in future versions:
*** ath compatibility modules.
*** gpgme_data_new_from_filepart
** --learn-code support
This might be integrated with import. we still need to work out how
to learn a card when gpg and gpgsm have support for smartcards.
-** How to terminate a pending operation? Something like gpgme_op_reset,
- but where are you allowed to call it (think callback handlers).
- Then gpgme_op_*list_end can go. Update: The only place where this
- can go is returning errors from callback handlers, and a function
- to be called for example from the user event loop code. The user
- must observe the threading rules! A blocking thread can not be
- cancelled.
** Might need a stat() for data objects and use it for length param to gpg.
** Allow to export secret keys.
** Implement support for photo ids.