Symantec 14541094 Implementation Guide - Page 49

Working with custom commands, Creating custom commands

Page 49 highlights

Configuring custom commands 49 Working with custom commands ■ Build the custom command. See "Building custom commands" on page 57. ■ Test the custom command. See "Testing custom commands" on page 57. Working with custom commands In the Symantec Packager main window, the Configure Products tab lists the custom commands that you have created and provides information about when they were last modified and built. You can create, edit, and delete custom commands and view details in this window. The Configure Products tab displays the product and command configuration files that are stored in the Configure Products folder that is specified in Symantec Packager Preferences. Creating custom commands The first step in configuring a custom command is to create a custom command file. This opens the Command Editor dialog box, which lets you configure and build the custom command. Like product configuration files, custom command files are saved with .pcg file extensions. Table 6-1 includes information about the configuration options. Table 6-1 Command Editor options Tab Description For more information Parameters Lets you configure a custom command that includes a command-line argument and the required and optional switches to use when the command runs. See "Specifying command-line parameters and switches" on page 52. See "Including files in a command" on page 54. Also lets you include additional files, such as batch files, scripts, or executable files, in a custom command. Operating Systems Lets you specify operating system support for the custom command. See "Specifying operating system support" on page 55.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96

49
Configuring custom commands
Working with custom commands
Build the custom command.
See
“Building custom commands”
on page 57.
Test the custom command.
See
“Testing custom commands”
on page 57.
Working with custom commands
In the Symantec Packager main window, the Configure Products tab lists the
custom commands that you have created and provides information about when
they were last modified and built. You can create, edit, and delete custom
commands and view details in this window.
The Configure Products tab displays the product and command configuration
files that are stored in the Configure Products folder that is specified in
Symantec Packager Preferences.
Creating custom commands
The first step in configuring a custom command is to create a custom command
file. This opens the Command Editor dialog box, which lets you configure and
build the custom command. Like product configuration files, custom command
files are saved with .pcg file extensions.
Table 6-1
includes information about the configuration options.
Table 6-1
Command Editor options
Tab
Description
For more information
Parameters
Lets you configure a custom
command that includes a
command-line argument and the
required and optional switches to
use when the command runs.
Also lets you include additional
files, such as batch files, scripts,
or executable files, in a custom
command.
See
“Specifying command-line
parameters and switches”
on
page 52.
See
“Including files in a
command”
on page 54.
Operating Systems
Lets you specify operating
system support for the custom
command.
See
“Specifying operating
system support”
on page 55.