|Skip Navigation Links|
|Exit Print View|
|man pages section 3: Extended Library Functions Oracle Solaris 10 1/13 Information Library|
- add or remove a dependent component
cc [flag …] file …-lwsreg [library …] #include <wsreg.h> int wsreg_add_dependent_component(Wsreg_component *comp, const Wsreg_component *dependentComp);
int wsreg_remove_dependent_component(Wsreg_component *comp, const Wsreg_component *dependentComp);
Wsreg_component **wsreg_get_dependent_components(const Wsreg_component *comp);
The wsreg_add_dependent_component() function adds the component specified by dependentComp to the list of dependent components contained in the component specified by comp.
The wsreg_remove_dependent_component() function removes the component specified by dependentComp from the list of dependent components contained in the component specified by comp.
The wsreg_get_dependent_components() function returns the list of dependent components contained in the component specified by comp.
The wsreg_add_dependent_component() function returns a non-zero value if the specified dependent component was successfully added; otherwise, 0 is returned.
The wsreg_remove_dependent_component() function returns a non-zero value if the specified dependent component was successfully removed; otherwise, 0 is returned.
The wsreg_get_dependent_components() function returns a null-terminated array of Wsreg_component pointers that represents the specified component's list of dependent components. If the specified component has no dependent components, NULL is returned. The resulting array must be released by the caller through a call to wsreg_free_component_array(). See wsreg_create_component(3WSREG).
The relationship between two components in which one must be installed for the other to be complete is a dependent/required relationship. The component that is required by the other component is the required component. The component that requires the other is the dependent component.
The required component must be installed and registered before the dependent component can be. Uninstaller applications should check the registry before uninstalling and unregistering components so a successful uninstallation of one product will not result in another product being compromised.
Read access to the product install registry is required to use these functions because these relationships are held with lightweight component references that can only be fully resolved using the registry contents.
The act of registering a component having required components results in the converse dependent relationships being established automatically.
See attributes(5) for descriptions of the following attributes: