is_drd_safe Attribute Policy
Release | Package | Policy |
| Type |
|
11i v2 | Patches | Attribute does not need to be set for 11i v2 patches. |
|
| Though all new |
|
| after November 1, 2004) must be |
|
| to set the is_drd_safe attribute. All existing patches have |
|
| been checked and all but a small subset have been verified to be |
|
| safe. The small subset of unsafe patches will be handled |
|
| internally. As a result, even though the patches will not have the |
|
| attribute set, they will be assumed to be safe (that is, the attribute |
|
| defaults to true for 11i v2 patches). All other packages have a |
|
| default of false. This difference in behavior for 11i v2 patches |
|
| has been introduced to allow existing 11i v2 patches (most of |
|
| which are safe) to be installed in a runcmd environment without |
|
| requiring the patches to be superseded just to set the attribute. |
11i v2 | Products | If a product |
|
| is_drd_safe attribute should be set to true for all filesets |
|
| within the product; otherwise, it should not be set for any of the |
|
| filesets. |
11i v3 | All | Required to be true for almost all |
| packages | OE contents, and all other software. Exceptions are firmware |
(and |
| patches and a few OpenView products. |
later) |
|
|