Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
View | Details | Raw Unified | Return to bug 424117
Collapse All | Expand All

(-)a/ebuild-writing/variables/text.xml (-3 / +3 lines)
Lines 215-223 The following variables may or must be defined by every ebuild. Link Here
215
  <tr>
215
  <tr>
216
    <ti><c>PDEPEND</c></ti>
216
    <ti><c>PDEPEND</c></ti>
217
    <ti>
217
    <ti>
218
    A list of packages to be installed after the package
218
    A list of packages to be installed (if possible) after the package
219
    is merged. Should only be used where <c>RDEPEND</c> is not
219
    is merged. Use this only when <c>RDEPEND</c> would cause cyclic
220
    possible. See <uri link="::general-concepts/dependencies"/>.
220
    dependencies. See <uri link="::general-concepts/dependencies"/>.
221
    </ti>
221
    </ti>
222
  </tr>
222
  </tr>
223
  <tr>
223
  <tr>
(-)a/general-concepts/dependencies/text.xml (-5 / +6 lines)
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
- 

Return to bug 424117