 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Use the CapabilityDependencies section in a component definition file to associate capabilities with other capabilities on which they depend or with which they conflict.
Under the CapabilityDependencies section, type the section syntax as follows:
Section syntax
Capability number, dependent capability number, dependency type
| Capability number | Use the capability numbers as you defined them in the Capabilities section. |
| dependent capability number | Use the capability numbers as you defined them in the Capabilities section. |
| dependency type |
Yor blank = Capability requires the presence of the
dependent capability (default)
N= Capability conflicts with the dependent capability and is mutually exclusive Note You can limit a user to one component selection from this capability by making the capability conflict with itself. |
Syntax example
| Capability dependencies example | In this example, the Mouse capability is dependent
on the Core OS:
[Capabilities] 1 = Mouse 2 = ''Core OS'' [CapabilityDependencies] 1,2 |
| Capability conflicts example | In this example, the configuration allows only one
keyboard driver and one keyboard layout.
[Capabilities] 1 = Keyboard drivers 2 = Keyboard layout 3 = Keyboard input locale [CapabilityDependencies] 1, 1, N 2, 2, N |