git: 6fca32fd5f - main - [phb]: Document the use of Makefile.crates

The branch main has been updated by fernape:

URL: https://cgit.FreeBSD.org/doc/commit/?id=6fca32fd5f3e253458303acd71c44ed6a6c9bd4d

commit 6fca32fd5f3e253458303acd71c44ed6a6c9bd4d
Author:     Fernando Apesteguía <[email protected]>
AuthorDate: 2023-03-17 11:49:38 +0000
Commit:     Fernando Apesteguía <[email protected]>
CommitDate: 2023-03-17 16:19:41 +0000

    [phb]: Document the use of Makefile.crates
    
    Some people don't know about this.
    
    Reviewed by:            carlavilla
    Differential Revision:  https://reviews.freebsd.org/D39143
---
 documentation/content/en/books/porters-handbook/special/_index.adoc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/documentation/content/en/books/porters-handbook/special/_index.adoc b/documentation/content/en/books/porters-handbook/special/_index.adoc
index 4ebeb7f84e..9221eef41d 100644
--- a/documentation/content/en/books/porters-handbook/special/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/special/_index.adoc
@@ -505,6 +505,9 @@ For ports that use Cargo, define `USES=cargo`.
 |`CARGO_CRATES`
 |
 |List of crates the port depends on. Each entry needs to have a format like `cratename-semver` for example, `libc-0.2.40`. Port maintainers can generate this list from [.filename]#Cargo.lock# using `make cargo-crates`. Manually bumping crate versions is possible but be mindful of transitive dependencies.
+If the list generated by `make cargo-crates` is big, it might be convenient to place it inside a `Makefile.crates` file in the top-level port directory.
+If present, the ports framework sources that file automatically.
+This helps keeping the main port Makefile withing a reasonable size.
 
 |`CARGO_FEATURES`
 |