diff options
| author | Morgan Jones <me@numin.it> | 2025-04-07 00:16:10 -0700 |
|---|---|---|
| committer | Morgan Jones <me@numin.it> | 2025-04-09 00:49:47 -0700 |
| commit | e3807568adf07e757d01fb8a20f3d79fcabfc61b (patch) | |
| tree | 5176552b09c9bf09b738dde6f1f303dea4e5acaf /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | 8e7cc728eb122b728913ff497946bb3fb494c280 (diff) | |
tpm2-pkcs11: fix fapi configure option; split tpm2-pkcs11-{esapi,fapi}
Per documentation at:
https://github.com/tpm2-software/tpm2-pkcs11/blob/master/docs/FAPI.md
the ESAPI support for tpm2-pkcs11 creates a fundamentally different
package, so split it into two new attributes: tpm2-pkcs11-esapi and
tpm2-pkcs11-fapi.
The existing package is unchanged, supporting both FAPI and esysdb, and
also requiring TPM2_PKCS11_BACKEND=fapi to be exported to use FAPI.
The tpm2-pkcs11-esapi attribute has fapi support compiled out and uses
esysdb all the time.
The tpm2-pkcs11-fapi attribute takes the extra step of applying a patch
that causes tpm2-pkcs11 to default to using FAPI, without needing to
export TPM2_PKCS11_BACKEND=fapi. However, TPM2_PKCS11_BACKEND=esysdb can
still be exported and will work.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions