public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] DEPEND/RDEPEND question
@ 2006-04-25  6:53 Alin Nastac
  2006-04-25  7:13 ` Harald van Dijk
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Alin Nastac @ 2006-04-25  6:53 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

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?
I know that when a package is installed the usual way (not from a binary
tarball) dependencies==RDEPEND+DEPEND, but portage functionality could
change in the future. It may not be the wisest decision ever made, but
portage could very well remove whatever dependencies are found in DEPEND
- RDEPEND, once the package is installed.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] DEPEND/RDEPEND question
  2006-04-25  6:53 [gentoo-dev] DEPEND/RDEPEND question Alin Nastac
@ 2006-04-25  7:13 ` Harald van Dijk
  2006-04-25  8:24 ` Alec Warner
  2006-04-30 13:52 ` Carsten Lohrke
  2 siblings, 0 replies; 4+ messages in thread
From: Harald van Dijk @ 2006-04-25  7:13 UTC (permalink / raw
  To: gentoo-dev

On Tue, Apr 25, 2006 at 09:53:58AM +0300, 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?

Unless there's been a change I'm not aware of, that's right. You should
often use something similar to
 COMMON="..."
 DEPEND="$COMMON ..."
 RDEPEND="$COMMON ..."
when not exactly all of $DEPEND is part of RDEPEND or vice versa though.

> I know that when a package is installed the usual way (not from a binary
> tarball) dependencies==RDEPEND+DEPEND, but portage functionality could
> change in the future. It may not be the wisest decision ever made, but
> portage could very well remove whatever dependencies are found in DEPEND
> - RDEPEND, once the package is installed.

You already mentioned binary packages. In addition to that, I think bad
dependencies can break things even under current portage versions by
building with ROOT set.

Something worth noting is that if RDEPEND is unset, it defaults to
$DEPEND, so in some cases, DEPEND="..." can be enough even if there are
also runtime dependencies. However, if RDEPEND is set at all, it should
be complete (except that system packages of course can be omitted).
-- 
gentoo-dev@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] DEPEND/RDEPEND question
  2006-04-25  6:53 [gentoo-dev] DEPEND/RDEPEND question Alin Nastac
  2006-04-25  7:13 ` Harald van Dijk
@ 2006-04-25  8:24 ` Alec Warner
  2006-04-30 13:52 ` Carsten Lohrke
  2 siblings, 0 replies; 4+ messages in thread
From: Alec Warner @ 2006-04-25  8:24 UTC (permalink / raw
  To: gentoo-dev

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?
> I know that when a package is installed the usual way (not from a binary
> tarball) dependencies==RDEPEND+DEPEND, but portage functionality could
> change in the future. It may not be the wisest decision ever made, but
> portage could very well remove whatever dependencies are found in DEPEND
> - RDEPEND, once the package is installed.

It needs to be in both.  For example if you only set it in DEPEND,
merging to ROOT!=/ would break as the dep would get installed in / and
not ROOT, so the app would fail to run.

-Antarus
-- 
gentoo-dev@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] DEPEND/RDEPEND question
  2006-04-25  6:53 [gentoo-dev] DEPEND/RDEPEND question Alin Nastac
  2006-04-25  7:13 ` Harald van Dijk
  2006-04-25  8:24 ` Alec Warner
@ 2006-04-30 13:52 ` Carsten Lohrke
  2 siblings, 0 replies; 4+ messages in thread
From: Carsten Lohrke @ 2006-04-30 13:52 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-04-30 13:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-25  6:53 [gentoo-dev] DEPEND/RDEPEND question Alin Nastac
2006-04-25  7:13 ` Harald van Dijk
2006-04-25  8:24 ` Alec Warner
2006-04-30 13:52 ` Carsten Lohrke

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox