From 034092ae498c15ed031f2cf7412ad285dea7e6ee Mon Sep 17 00:00:00 2001 From: r00t Date: Sun, 20 Aug 2017 07:25:55 -0400 Subject: [PATCH] updating docs --- docs/manual/HEAD.adoc | 2 +- docs/manual/user/BUILDINI.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/HEAD.adoc b/docs/manual/HEAD.adoc index 8d93a43..32cd684 100644 --- a/docs/manual/HEAD.adoc +++ b/docs/manual/HEAD.adoc @@ -1,6 +1,6 @@ = BDisk User and Developer Manual Brent Saner -v1.2, 2017-05-11 +v1.3, 2017-08-20 :doctype: book :data-uri: :imagesdir: images diff --git a/docs/manual/user/BUILDINI.adoc b/docs/manual/user/BUILDINI.adoc index b9117b3..2ac170c 100644 --- a/docs/manual/user/BUILDINI.adoc +++ b/docs/manual/user/BUILDINI.adoc @@ -3,7 +3,7 @@ This file is where you can specify some of the very basics of BDisk building. It It's single-level, but divided into "sections". This is unfortunately a limitation of ConfigParser, but it should be easy enough to follow. -Blank lines are ignored, as well as any lines beginning with `#` and `;`. There are some restrictions and recommendations for some values, so be sure to note them when they occur. Variables referencing other values in the `build.ini` are allowed in the format of `${value}` if it's in the same section; otherwise, `${section:value}` can be used. +Blank lines are ignored, as well as any lines beginning with `#` and `;`. There are some restrictions and recommendations for some values, so be sure to note them when they occur. Variables referencing other values in the `build.ini` are allowed in the format of `${keyname}` if it's in the same section; otherwise, `${section:keyname}` can be used. If you want to use your own `build.ini` file (and you should!), the following paths are searched in order. The first one found will be used.