From f7050588bc76901e0a147c158e64ac3140dc8bfd Mon Sep 17 00:00:00 2001 From: Rich Salz Date: Fri, 30 Apr 2021 12:18:00 -0400 Subject: Add .includedir pragma Also add a negative test, and fix typo's. Reviewed-by: Dmitry Belyavskiy Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/15090) --- doc/man5/config.pod | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc/man5') diff --git a/doc/man5/config.pod b/doc/man5/config.pod index 6b800b96e1..ad7d7e1e01 100644 --- a/doc/man5/config.pod +++ b/doc/man5/config.pod @@ -48,7 +48,7 @@ while scanning a directory, and that file has an B<.include> directive that specifies a directory, that is also ignored. As a general rule, the B should be an absolute path; this can -be enforced with the B pragma, described below. +be enforced with the B and B pragmas, described below. The environment variable B, if it exists, is prepended to all relative pathnames. If the pathname is still relative, it is interpreted based on the @@ -57,7 +57,7 @@ current working directory. To require all file inclusions to name absolute paths, use the following directive: - .progma [=] abspath:value + .pragma [=] abspath:value The default behavior, where the B is B or B, is to allow relative paths. To require all B<.include> pathnames to be absolute paths, @@ -76,6 +76,13 @@ C followed by the expansion of the variable C. If B is B or B, then C is a single seven-character name nad variable expansions must be specified using braces or parentheses. + .pragma [=] includedir:value + +If a relative pathname is specified in the B<.include> directive, and +the B environment variable doesn't exist, then +the value of the B pragma, if it exists, is prepended to the +pathname. + =head2 Settings A configuration file is divided into a number of I. A section -- cgit v1.2.3