The optional GROUP block describes a group of packages.

This can only be specified at the root level in the script, i.e. in the WARPIN block. See the "Installation Scripts" page for an overview where this element should be placed.

Items which belong to the same group are displayed below the group item in the tree view on the "Container" page. The user can expand and collapse the group similar to Workplace Shell tree views.

Note: Groups are not evaluated during the actual installation process. There is no corresponding concept in the archive file, and groups are not stored in the global database of installed packages either. All this is based on packages only.

The only purpose of groups is to give the user a visual clue on the "Container" page that certain packages have similar characteristics and to allow him/her to select a group of packages at once.

You can specify as many groups as you like, i.e. no group, one group or several groups. You may also nest GROUP blocks. However, you cannot specify one package to appear in several groups at once. This is not checked for, but will definitely lead to problems.

Syntax:

<GROUP
    TITLE="title"
    EXPANDED="{YES|NO}"
>
    <PCK ...> ... </PCK>
    ...
</GROUP>
In between the <GROUP> and </GROUP> tags, you must specifiy at least one <PCK> element for the packages to be contained in that group.

Attributes:


TITLE="title"
Required. This specifies the title of the group as it is shown on WarpIN's container page. This is only used for that display and not stored anywhere (since groups aren't stored in the first place).
EXPANDED="{YES|NO}"
Optional. If EXPANDED="YES" specified, the group is initially expanded in the tree view of the "Container" page. Otherwise (EXPANDED="NO", which is the default) it is collapsed, that is, the user will have to press the "+" button to view the group's packages.

Note that there are no other attributes for the <GROUP> element. Paths, indices, selections etc. are maintained individually for each package.

The selection status of the group depends solely on the selection status of the packages which are contained in that group. That is, if the user selects/deselects a group, all packages in it are selected/deselected. If the user selects/deselects a package, the selection status of the group to which the package belongs is updated automatically. If you want all packages of a group to be initially selected, you have to specify SELECT="YES" with the opening PCK tag of each package in the group.