1.4 In order to verify the integrity of the packages, keeping all these files in the current working directory, do this:
1.4.1: import the key from swbuild.asc to gpg and find the fingerprint;
1.4.2: confirm the fingerprint with SMART or your vendor channel;
1.4.3: sign the key with your own ultimately trusted key;
1.4.4: execute the command "./validate.sh" in order to verify the integrity of the package files you have received, and check the output; ignore any warnings about improperly formatted lines.

1.5 Once the packages are verified, you will first edit the customization file. It contains script variables preceded by comments that explain their meaning. For a remote silent mass deployment it is necessary to insert the product key obtained from SMART or your vendor channel. You may also wish to select which gallery components you need to make available

1.6 When the customization file is modified appropriately, you will execute "./customize.sh" which will modify all the .deb package files by inserting the contents of the customization file into the maintainer scripts of each package. At this point the .asc integrity files are remade and they are signed with the key specified on the SMART_ARCHIVE_KEY line, in the customization file. If SMART_ARCHIVE_KEY is not set, the current user's default key will be used for signing.

1.7 Once the packages have been customized, they can be installed with "dpkg -i" or inserted into your particular deployment framework.