C4 Data - Application Profile
-- list of (platform, medal) pairs
This defines which medal to show for this application in the application selection dialog. Currently there the official platforms are Mac, Linux, and Android. On any other platform CrossOver would show an 'untested' medal.
C4P uses these values:
- untested - Untested
- knownnottowork - Known not to work
- bronze - Bronze
- silver - Silver
- gold - Gold
C4 also has a supported/unsupported flag which varies the appearance of the medals: unbronze, unsilver, ungold
A slash-separated category path as defined by C4's set of application categories. That is this string is of the form 'category/sub-category/sub-sub-category', for instance 'Games/Racing Games'. This will be used to let the user filter the application list, or to present it as a tree.
-- list of strings
This is a list of flags that characterize the application. The currently supported flags are:
- component - This is applied to things like DCOM98, MSI, fonts.
- application - This is applied to regular applications like Office, QuickTime, etc.
- nsplugin - This is applied to all profiles that install Netscape plugins, even if we currently disable these plugins via IgnoreNSPluginDlls.
- virtual - This is applied to profiles that don't need an installer. This is for pure dependency profiles such as the Core Fonts profile, but also potentially for profiles that only tweak settings such as the registry.
This is the id of the C4 entry that contains the installation profile. The default is to set this to AppId
- This is needed because C4 has separate entries for each component of applications like Microsoft Office. So this field is used so we don't have to duplicate the MS Office 2000 installation profile for Word, Excel, PowerPoint, Access, etc.
-- regular expression
This is used to check whether the application is installed, and by the installer core to check whether the installation was successful. Contains a regular expression used to match the uninstall registry key returned by "uninstaller.exe --list".
-- regular expression
This is used to check whether the application is installed, and by the installer core to check whether the installation was successful. Contains a regular expression used to match the display name retrieved from the registry by "uninstaller.exe --list".
-- list of (key glob, value glob, data glob) tuples
... ... ...
This is used to check whether the application is installed, and by the installer core to check whether the installation was successful.
For each tuple in the list we try to find a registry key that matches the specified key glob, then a value in that key whose name matches the value glob, and then check if its contents, when converted to a string, matches the specified data glob. If the data glob is empty, then a value glob match is enough. If both the value and data globs are empty, then a key glob match is enough.
If we find a match for a given tuple then the application is deemed to be installed.
-- list of expandable restricted file globs
This is used to check whether the application is installed, and by the installer core to check whether the installation was successful. If any of the specified file globs matches, then the application is installed.
-- list of bottle types
This is the list of bottle types the application can be installed in. The preferred bottle type is the first one in the list.
Valid bottle types are:
BottleTemplates can have an optional parameter "purpose". purpose can be either "use" or "install". "use" is the default value and results in normal behavior. A BottleTemplate with the parameter "install" will only be valid when the profile is used as a PreDependency
but will not be presented as valid for the user when they choose to install this profile. This is useful for a profile where it functions best in a given BottleTemplate however it may be needed in other BottleTemplates for other applications, but does not function as well there.
This property is used to group related applications in the same bottle.
- This is different from dependencies. Obviously Visio can very well work without MS Office.
- If an application should belong to two groups, then it probably means the two groups should be merged.
- This assumes that the default policy is to install each application in a separate bottle, and this mechanism is a way to override that mechanism.
- This setting has no effect on Android.
-- list of (language code, URL) pairs
For each language, the URL to the downloadable installer.
-- localizable URL
The URL of a web page from which the installer can be downloaded.
This field lets us handle upgrades to components which something an automated analysis of the profile dependencies and their properties cannot do.
Also note that this field is not a dependency. This makes it possible to handle 'upgrades' that are in fact full installers and don't need the item they are upgrading to be installed first.
This makes it relatively easy to suggest installing upgrades for already installed applications.
This setting has no effect on Android.
This field lets us handle games that are available through steam.
If this field is set to the proper Steam ID for the game then Steam is listed for the user as an available Install source. If the user selects Steam as the install source then we install steam in the bottle (if it is not present) and then pass this ID to steam to have it guide the user through the install.