User's Guide

Creating feature config maps

You can indicate the exact level of the feature and the valid platforms by using keys in the comment field of the config map. The two keys are:

vaVersionId
The vaVersionId key specifies the exact level of the feature. The value is a three digit number. For example, to specify that this config map is for VisualAge Smalltalk Version 5.5, use the following:
vaVersionId=550

isValid
The isValid key specifies whether a feature is valid for the image. The value can contain different information, however, the Smalltalk expression must evaluate to a boolean. For example, to specify what the valid operating systems are for a feature, use the following:
isValid=AbtCommonProductInstallerApp validPlatformIds:'woahs'

Where w = Windows, o = OS/2, a = AIX, h = HP-UX, s = SunOS.

For a feature to be displayed in the load feature list for an image, the vaVersionId must be less than or equal to the client image version and the isValid value must evaluate to true for at least one version of the feature config map. For example, if you build a feature on VisualAge Smalltalk Version 5.5, the vaVersionId for your feature will be 550. If IBM ships a fixpack for Version 5.5, the version ID will be something like 551. You will not need to update your version ID in this case because 550 is less than 551.

For information on creating config maps and adding required maps to a config map, see the IBM Smalltalk User's Guide.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]