C.2.6 Defining the Tasks to Run

VTEST can perform several pre-defined tasks. The configuration which task is performed on a certain package is defined via the $tasklist variable in the file vtestclient.pl. The following example defines the tasks for the packages basesystem, baselib and base++.

   $tasklist->{'basesystem'} = [ $task_rmvroot, $task_extract, 
                                 $task_boot_compile, $task_boot_install, 
                                 $task_selftest 
                               ];
   
   $tasklist->{'baselib'}    = [ $task_extract, $task_build, 
                                 $task_selftest 
                               ];
   $tasklist->{'base++'}     = [ $task_extract, $task_build, 
                                 $task_selftest 
                               ];

The pre-defined tasks available in this configuration are:

• $task_rmvroot. This task is used to clean the VROOT directory of VMAKE. This directory holds installed packages from previous runs of VMAKE and must be cleaned before the building process of a stand-alone package is started. However, the VROOT directory must not be cleaned for packages that depend on each other.

• $task_extract. This task extracts the package into the file system of the target architecture.

• $task_boot_compile. Task to bootstrap the VMAKE utility.

• $task_boot_install. Task to install the VMAKE utility in the VROOT directory of VMAKE.

• $task_selftest. Starts VMAKE in the selftest mode.

• $task_build. Builds a package.

2003-03-27