Attachment #225383 for bug #256271

View | Details | Raw Unified | Return to bug 256271
Collapse All | Expand All

Lines 4328-4334 For any of these dependency types: Link Here

(-)b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc (-2 / +2 lines)
4328	* `LIB_DEPENDS`	4328	* `LIB_DEPENDS`
4329	* `RUN_DEPENDS`	4329	* `RUN_DEPENDS`
4330		4330
4331	When option _OPT_ is selected, the value of `PT_DEPTYPE`, if defined, is appended to `DEPTYPE`. `OPT_DEPTYPE_OFF` works the same, but when `OPT` is _not_ selected. For example:	4331	When option _OPT_ is selected, the value of `OPT_DEPTYPE`, if defined, is appended to `DEPTYPE`. `OPT_DEPTYPE_OFF` works the same, but when `OPT` is _not_ selected. For example:
4332		4332
4333	[.programlisting]	4333	[.programlisting]
4334	....	4334	....
Lines 4760-4766 These macros do not add the installed files to [.filename]#pkg-plist#. They must Link Here
4760	[[install-documentation]]	4760	[[install-documentation]]
4761	=== Install Additional Documentation	4761	=== Install Additional Documentation
4762		4762
4763	If the software has some documentation other than the standard man and info pages that is useful for the user, install it under `DOCSDIR` This can be done, like the previous item, in the `post-install` target.	4763	If the software has some documentation other than the standard man and info pages that is useful for the user, install it under `DOCSDIR`. This can be done, like the previous item, in the `post-install` target.
4764		4764
4765	Create a new directory for the port. The directory name is `DOCSDIR`. This usually equals `PORTNAME`. However, if the user might want different versions of the port to be installed at the same time, the whole `PKGNAME` can be used.	4765	Create a new directory for the port. The directory name is `DOCSDIR`. This usually equals `PORTNAME`. However, if the user might want different versions of the port to be installed at the same time, the whole `PKGNAME` can be used.
4766		4766

Lines 38-44 Some ports, particularly the `p5-` ports, need to change their [.filename]#pkg-p Link Here

(-)b/documentation/content/en/books/porters-handbook/plist/_index.adoc (-1 / +1 lines)
38		38
39	To make other substitutions, set `PLIST_SUB` with a list of `_VAR=VALUE_` pairs and instances of `%%_VAR_%%` will be substituted with _VALUE_ in [.filename]#pkg-plist#.	39	To make other substitutions, set `PLIST_SUB` with a list of `_VAR=VALUE_` pairs and instances of `%%_VAR_%%` will be substituted with _VALUE_ in [.filename]#pkg-plist#.
40		40
41	For instance, if a port installs many files in a version-specific subdirectory, use a placeholder for the version so that [.filename]#pkg-plist# does not have to be regenerated every time the port is updated. For example:	41	For instance, if a port installs many files in a version-specific subdirectory, use a placeholder for the version so that [.filename]#pkg-plist# does not have to be regenerated every time the port is updated. For example, set:
42		42
43	[.programlisting]	43	[.programlisting]
44	....	44	....

Lines 161-167 USE_LDCONFIG= ${PREFIX}/lib/foo ${PREFIX}/lib/bar Link Here

(-)b/documentation/content/en/books/porters-handbook/special/_index.adoc (-1 / +1 lines)
161		161
162	Please double-check, often this is not necessary at all or can be avoided through `-rpath` or setting `LD_RUN_PATH` during linking (see package:lang/mosml[] for an example), or through a shell-wrapper which sets `LD_LIBRARY_PATH` before invoking the binary, like package:www/seamonkey[] does.	162	Please double-check, often this is not necessary at all or can be avoided through `-rpath` or setting `LD_RUN_PATH` during linking (see package:lang/mosml[] for an example), or through a shell-wrapper which sets `LD_LIBRARY_PATH` before invoking the binary, like package:www/seamonkey[] does.
163		163
164	When installing 32-bit libraries on 64-bit system, use `USE_LDCONFIG32` instead.	164	When installing 32-bit libraries on a 64-bit system, use `USE_LDCONFIG32` instead.
165		165
166	If the software uses <<using-autotools,autotools>>, and specifically `libtool`, add crossref:uses[uses-libtool,`USES=libtool`].	166	If the software uses <<using-autotools,autotools>>, and specifically `libtool`, add crossref:uses[uses-libtool,`USES=libtool`].
167		167

Return to bug 256271