Gentoo Archives: gentoo-user

From: Rich Freeman <rich0@g.o>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: CDEPEND
Date: Tue, 26 Apr 2016 10:35:57
Message-Id: CAGfcS_noqha5kwdZhMA2b7b5V-b6LY-=frukPJTgSaQLZzUZgQ@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: CDEPEND by Sam Jorna
1 On Mon, Apr 25, 2016 at 10:54 PM, Sam Jorna <wraeth@g.o> wrote:
2 > On Tue, Apr 26, 2016 at 02:41:23AM +0000, James wrote:
3 >> Do you have a definition of exactly what a CDEPEND is?
4 >
5 > CDEPEND is a commonly used name for COMMON_DEPEND - dependencies shared between
6 > DEPEND and RDEPEND (and, potentially, PDEPEND). In cases where you have a fair
7 > number of shared dependencies, and one or two in only DEPEND or RDEPEND, you
8 > could enter the common ones in a variable (commonly CDEPEND) and add that to
9 > your {,R}DEPEND definition.
10 >
11 > Use of CDEPEND is common, but not policy. You can find other examples of it's
12 > usage with `qgrep -H CDEPEND` (qgrep is provided by app-portage/portage-utils).
13 >
14
15 Just in case it wasn't obvious from your explanation above, portage
16 completely ignores the contents of the CDEPEND variable. It is just
17 used interally within the ebuild and as you pointed out it gets
18 included in RDEPEND/DEPEND which is what portage uses.
19
20 This is why it isn't in any of the official docs. If you edited an
21 ebuild and replaced all occurrences of CDEPEND with MY_VAR_NAME it
22 would work exactly the same.
23
24 Using it is generally a good practice all the same, unless the DEPENDs
25 really are RDEPENDs as well (which isn't always the case).
26
27 --
28 Rich