Delta Block Syntax
The syntax of a delta block is as follows:
start_pref_delta
[ source_version : AA.b ]
preferences : tag1 [, tag2…]
transformation : module_name, func_name [, arg1 [, arg2]]
or special keyword
end_pref_delta
Note that square brackets ([]) indicate optional fields.
The following table lists the delta block fields.
Table 15: Delta Block Fields
| Field | Description |
|---|---|
| start_pref_delta | Specifies the start of a delta block. |
| source_version : AA.b | Specifies the release from which to migration. For example: 12.0. If this field is omitted, the transformation is always applied to the specified preferences, regardless of the preferences file from which the preferences are being migrated. |
| preferences : tag1 [, tag2...] | Specifies one or more preference tags. When multiple preferences are specified, separate each preference with a space and a comma. |
| transformation : module_name, func_name [, arg1 [arg2]] or special keyword | Specifies the migration and conversion information. - module_name – Specifies a module name. - func_name – Specifies the name of a function within the specified module. - [, arg1 [,arg2]] – Specifies arguments to a conversion function. A conversion function takes one argument and returns a value indicating the status of the transformation. For more information, see Delta Block Function Arguments and Accessor/Mutator Functions. - special keyword – Specifies common transformations. You can use the following keywords: do_not_migrate Specifies to suppress the migration of the list preferences. release_path_convert Converts paths to the release directory of the upgraded software. For example, if migrating from 12.0 to 12.2, then the path values containing the string “12.0” are replaced with “12.2”. |
| end_pref_delta | Specifies the end of a delta block. |