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