| commit | de43d00db071a04653cff592607647bb9c01d025 | |
| author | Dan McGee <dan@archlinux.org> | |
| Wed, 24 Aug 2011 18:24:42 +0000 (24 13:24 -0500) | ||
| committer | Dan McGee <dan@archlinux.org> | |
| Mon, 29 Aug 2011 00:51:54 +0000 (28 19:51 -0500) | ||
| tree | 9ad6cc271d87124a6d8004a76e53f16f052d222c | treesnapshot (tar.gz zip) |
| parent | 12387ca4e5c16994bacad52c142ef94868ba545a | commitdiff |
Refactor signature result return format
I was trying to take a shortcut and not introduce a wrapper struct for
the signature results, so packed it all into alpm_sigresult_t in the
first iteration. However, this is painful when one wants to add new
fields or only return information regarding a single signature.
Refactor the type into a few components which are exposed to the end
user, and will allow a lot more future flexibility. This also exposes
more information regarding the key to the frontend than was previously
available.
The "private" void *data pointer is used by the library to store the
actual key object returned by gpgme; it is typed this way so the
frontend has no expectations of what is there, and so we don't have any
hard gpgme requirement in our public API.
Signed-off-by: Dan McGee <dan@archlinux.org>
I was trying to take a shortcut and not introduce a wrapper struct for
the signature results, so packed it all into alpm_sigresult_t in the
first iteration. However, this is painful when one wants to add new
fields or only return information regarding a single signature.
Refactor the type into a few components which are exposed to the end
user, and will allow a lot more future flexibility. This also exposes
more information regarding the key to the frontend than was previously
available.
The "private" void *data pointer is used by the library to store the
actual key object returned by gpgme; it is typed this way so the
frontend has no expectations of what is there, and so we don't have any
hard gpgme requirement in our public API.
Signed-off-by: Dan McGee <dan@archlinux.org>