Lines 56-65
Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> could <e>in theory</e> b
Link Here
|
56 |
<body> |
56 |
<body> |
57 |
|
57 |
|
58 |
<p> |
58 |
<p> |
59 |
The <c>PDEPEND</c> variable specifies dependencies which must be merged <e>after</e> the |
59 |
The <c>PDEPEND</c> variable specifies dependencies that should be |
60 |
package. This is sometimes used for plugins which have a dependency upon the |
60 |
merged <e>after</e> the package, but which may be merged at any time, |
61 |
package being merged. Generally <c>PDEPEND</c> should be avoided in favour of |
61 |
if the former is not possible. This is sometimes used for plugins |
62 |
<c>RDEPEND</c> except where this will create circular dependency chains. |
62 |
that have a dependency upon the package being merged. Generally |
|
|
63 |
<c>PDEPEND</c> should be avoided in favour of <c>RDEPEND</c> except |
64 |
where this will create circular dependency chains. |
63 |
</p> |
65 |
</p> |
64 |
|
66 |
|
65 |
</body> |
67 |
</body> |
66 |
- |
|
|