Add repo-split migration guide #511
No reviewers
Labels
No labels
api-break
approved
bug
component-docs
component-platform
component-test
dependencies
deprecation
DO-NOT-MERGE
enhancement
good first issue
help wanted
needs-adoption
needs-backports
needs-ci
needs-design-approval
needs-info
needs-preceding-pr
needs-review
needs-reviewer
needs-work
priority-high
priority-low
priority-medium
priority-scheduled
priority-very-high
resolved-after-1.1
single-reviewer
size-l
size-m
size-optimisation
size-s
size-xs
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Mbed-TLS/TF-PSA-Crypto!511
Loading…
Reference in a new issue
No description provided.
Delete branch "migration-guide"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Fixes https://github.com/Mbed-TLS/mbedtls/issues/10248
PR checklist
LGTM except that a couple of things are different in TF-PSA-Crypto.
@ -0,0 +1,172 @@## CMake as the only build systemThere's no
libtarget. (I've already grumbled about that.)I already mentioned this in mbedtls, and it's more important to be accurate here: not just the PSA Cryptography API, there are a few extensions. These extensions are available in TF-PSA-Crypto even though most of them have function names that begin with
mbedtls_, so it's especially important to be clear that the distinction is crypto vs the rest, not PSA vs the rest.Suggested wording:
The run-on sentence makes it look like there's a build system with three parts, and then the words “are not supported” breaks the grammar.
@ -0,0 +155,4 @@- Using the TF-PSA-Crypto pkg-config file.- Using TF-PSA-Crypto as an installed library.### Developer or package maintainersHere, an important note is that if you want to provide both crypto and X.509(+TLS), you need to package Mbed TLS and its bundled TF-PSA-Crypto. You can't have both Mbed TLS and the standalone TF-PSA-Crypto.
@ -0,0 +155,4 @@- Using the TF-PSA-Crypto pkg-config file.- Using TF-PSA-Crypto as an installed library.### Developer or package maintainersI've added a new point but I do not really understand what you want to convey here thus I am not sure about it.
LGTM
@ -0,0 +155,4 @@- Using the TF-PSA-Crypto pkg-config file.- Using TF-PSA-Crypto as an installed library.### Developer or package maintainersTF-PSA-Crypto and Mbed TLS now appear to be separate products. If a distribution means to include both, the natural expectation is to first configure and build TF-PSA-Crypto, then configure and build Mbed TLS against the TF-PSA-Crypto that was previously built. But we don't offer a way to do that. Instead, to provide both TF-PSA-Crypto and Mbed TLS, you need to configure and build Mbed TLS, and ship the TF-PSA-Crypto that it bundles.
LGTM, I found some small nits but they are not a blocker on their own.
@ -0,0 +95,4 @@#### Using TF-PSA-Crypto as a CMake subprojectThe base name of the static and shared cryptography libraries is now `tfpsacrypto`, formerly `mbedcrypto`.As before, this base name is also the base name of CMake targets to build the libraries.Non-blocker nit: Pluralisation and "formely" -> "formerly"
@ -0,0 +95,4 @@#### Using TF-PSA-Crypto as a CMake subprojectThe base name of the static and shared cryptography libraries is now `tfpsacrypto`, formerly `mbedcrypto`.As before, this base name is also the base name of CMake targets to build the libraries.I've used the plural because we build potentially two libraries: the static and the shared one. I've kept that. I've fixed "formely".
LGTM
LGTM, thanks!