wsreg_add_dependenProductnInstallRRegistrwsreg_add_dependent_component(3WSREG)NAME
wsreg_add_dependent_component, wsreg_remove_dependent_component,
wsreg_get_dependent_components - add or remove a dependent component
SYNOPSIS
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);
DESCRIPTION
The wsreg_add_dependent_component() function adds the component speci‐
fied 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 con‐
tained 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.
RETURN VALUES
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 compo‐
nent'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).
USAGE
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 com‐
ponent. The component that requires the other is the dependent compo‐
nent.
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 success‐
ful 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 compo‐
nent references that can only be fully resolved using the registry con‐
tents.
The act of registering a component having required components results
in the converse dependent relationships being established automati‐
cally.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
┌─────────────────────────────┬─────────────────────────────┐
│ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
├─────────────────────────────┼─────────────────────────────┤
│MT-Level │Unsafe │
└─────────────────────────────┴─────────────────────────────┘
SEE ALSOwsreg_add_required_component(3WSREG), wsreg_can_access_reg‐
istry(3WSREG), wsreg_create_component(3WSREG), wsreg_initial‐
ize(3WSREG), wsreg_register(3WSREG), attributes(5)SunOS 5.10 22 Sep wsreg_add_dependent_component(3WSREG)
