From e57e7f332fcf9ea26a7f7536b18a24181b680463 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=C3=A5kan=20Mattsson?= Date: Thu, 22 Apr 2010 09:30:12 +0200 Subject: Make some cleanups --- lib/reltool/doc/src/reltool.xml | 88 ++++++++++++++++++++--------------------- 1 file changed, 44 insertions(+), 44 deletions(-) (limited to 'lib/reltool/doc') diff --git a/lib/reltool/doc/src/reltool.xml b/lib/reltool/doc/src/reltool.xml index a46323b1f2..0c2b7d2a2b 100644 --- a/lib/reltool/doc/src/reltool.xml +++ b/lib/reltool/doc/src/reltool.xml @@ -136,16 +136,16 @@ incl_cond -

This parameter controls the application and escript - inclusion policy. It defaults to derived which means - that the applications that not have any explicit - incl_cond setting, will only be included if any other - (explicitly or implicitly included) application uses it. The - value include implies that all applications and - escripts that that not have any explicit incl_cond - setting will be included. exclude implies that all - applications and escripts) that that not have any explicit - incl_cond setting will be excluded.

+

This parameter controls the application and escript + inclusion policy. It defaults to derived which means + that the applications that not have any explicit + incl_cond setting, will only be included if any other + (explicitly or implicitly included) application uses it. The + value include implies that all applications and + escripts that that not have any explicit incl_cond + setting will be included. exclude implies that all + applications and escripts) that that not have any explicit + incl_cond setting will be excluded.

 boot_rel @@ -167,33 +167,33 @@ relocatable -

This parameter controls whether the erl executable - in the target system automatically should determine where it - is installed or if it should use a hardcoded path to the - installation. In the latter case the target system must be - installed with reltool:install/2 before it can be - used. If the system is relocatable, the file tree containing - the target system can be moved to another location without - re-installation. The default is true.

+

This parameter controls whether the erl executable + in the target system automatically should determine where it + is installed or if it should use a hardcoded path to the + installation. In the latter case the target system must be + installed with reltool:install/2 before it can be + used. If the system is relocatable, the file tree containing + the target system can be moved to another location without + re-installation. The default is true.

 profile -

The creation of the specification for a target system is - performed in two steps. In the first step a complete - specification is generated. It will likely contain much more - files than you are interested in your customized target - system. In the second step the specification will be filtered - according to your filters. There you have the ability to - specify filters per application as well as system wide - filters. You can also select a profile for your - system. Depending on the profile, different default - filters will be used. There are three different profiles to - choose from: development, embedded and - standalone. development is default. The - parameters that are affected by the profile are: - incl_sys_filters, excl_sys_filters, - incl_app_filters and excl_app_filters.

+

The creation of the specification for a target system is + performed in two steps. In the first step a complete + specification is generated. It will likely contain much more + files than you are interested in your customized target + system. In the second step the specification will be filtered + according to your filters. There you have the ability to + specify filters per application as well as system wide + filters. You can also select a profile for your + system. Depending on the profile, different default + filters will be used. There are three different profiles to + choose from: development, embedded and + standalone. development is default. The + parameters that are affected by the profile are: + incl_sys_filters, excl_sys_filters, + incl_app_filters and excl_app_filters.

 app_file @@ -386,14 +386,14 @@ incl_cond -

This parameter controls whether the module is included or not. By - default the mod_incl parameter on application and system level - will be used to control whether the module is included or not. The - value of incl_cond overrides the module inclusion policy. - include implies that the module is included, while - exclude implies that the module not is included. - derived implies that the is included if any included uses the - module.

+

This parameter controls whether the module is included or not. By + default the mod_incl parameter on application and system level + will be used to control whether the module is included or not. The + value of incl_cond overrides the module inclusion policy. + include implies that the module is included, while + exclude implies that the module not is included. + derived implies that the is included if any included uses the + module.

 debug_info @@ -479,7 +479,7 @@ re_regexp() = string() reason() = string() regexps() = [re_regexp()] | {add, [re_regexp()]} - | {del, [re_regexp()]} + | {del, [re_regexp()]} rel_file() = term() rel_name() = string() rel_vsn() = string() @@ -511,9 +511,9 @@ target_spec() = [target_spec()] create_target(Server, TargetDir) -> ok | {error, Reason} Create a target system - Server = server() + Server = server() TargetDir = target_dir() - Reason = reason() + Reason = reason()

Create a target system. Gives the same result as {ok,TargetSpec}=reltool:get_target_spec(Server) and -- cgit v1.2.3