From 51741a74b8ca509ca980f5e752fbcbb7fa2fe8fd Mon Sep 17 00:00:00 2001 From: Jens Schweikhardt Date: Tue, 20 Jan 2004 21:09:17 +0000 Subject: [PATCH] Document PATCH_DEPENDS. Correct some numbers. PR: 56452 Submitted by: Kang Liu --- .../books/porters-handbook/book.sgml | 22 +++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml index b90dc98d3c..9ad005c7e1 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.sgml +++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml @@ -2841,7 +2841,7 @@ PATCHFILES= patch1:test Dependencies - Many ports depend on other ports. There are five variables that + Many ports depend on other ports. There are seven variables that you can use to ensure that all the required bits will be on the user's machine. There are also some pre-supported dependency variables for common cases, plus a few more to control the behavior @@ -2993,11 +2993,29 @@ PATCHFILES= patch1:test + + <makevar>PATCH_DEPENDS</makevar> + + This variable specifies executables or files this port + requires to patch. Like the previous, it is a list of + path:dir:target + tuples. For example, PATCH_DEPENDS= + ${NONEXISTENT}:${PORTSDIR}/java/jfc:extract + will descend into the + java/jfc subdirectory of your ports tree to + build and install it if it is not found. + + The dependency is checked from within the + patch target. The + target part can be omitted if it is the + same as DEPENDS_TARGET. + + <makevar>DEPENDS</makevar> If there is a dependency that does not fall into either of the - above four categories, or your port requires having the source of + above categories, or your port requires having the source of the other port extracted in addition to having it installed, then use this variable. This is a list of dir:target,