1 |
On Tuesday 25 April 2006 08:53, Alin Nastac wrote: |
2 |
> Lets say a package foo depends on bar, both at compile time and run time. |
3 |
> Shouldn't DEPEND _and_ RDEPEND of the foo package reflect that |
4 |
> dependency? I usually set DEPEND="$RDEPEND ..." or vice-versa (depending |
5 |
> on which is the most demanding). Am I utterly wrong here? |
6 |
|
7 |
This is right, when there're more dependencies in DEPEND than in RDEPEND. If |
8 |
DEPEND == RDEPEND you should leave either one unset, as Portage assumes that |
9 |
DEPEND == RDEPEND in that case. |
10 |
|
11 |
|
12 |
To quote the ebuild policy: |
13 |
|
14 |
"The DEPEND variable inside your foo-x.y.z.ebuild tells Portage about which |
15 |
packages are needed to build foo. The RDEPEND variable specifies which |
16 |
packages are needed for foo to run. You only need to explicitly specify |
17 |
RDEPEND if the ebuild's runtime dependencies are different than what you |
18 |
specified in DEPEND; if not specified, RDEPEND will default to your DEPEND |
19 |
settings. Never set RDEPEND to DEPEND yourself in an ebuild." |
20 |
|
21 |
|
22 |
Carsten |