1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 07/09/12 02:46 PM, Michał Górny wrote: |
5 |
> On Fri, 7 Sep 2012 19:31:16 +0100 Ciaran McCreesh |
6 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
7 |
> |
8 |
>> On Fri, 7 Sep 2012 20:23:23 +0200 Michał Górny |
9 |
>> <mgorny@g.o> wrote: |
10 |
>>> I can't agree unless I am missing something. Doesn't the |
11 |
>>> majority of ebuilds actually require most of DEPEND (well, the |
12 |
>>> part common with RDEPEND) to be installed on the target? I'm |
13 |
>>> thinking of the shared libraries mostly. |
14 |
>> |
15 |
>> "The part common with RDEPEND" is a different issue. We're |
16 |
>> talking about what the usual thing to do is for dependencies that |
17 |
>> are in DEPEND but not RDEPEND. A typical example here is a binary |
18 |
>> that is executed as part of the build process. |
19 |
> |
20 |
> Thanks for keeping me on the topic. |
21 |
> |
22 |
> Now, let me remind you because you probably fail to know the world |
23 |
> outside your dreamworld: |
24 |
> |
25 |
> (with HDEPEND/DEPEND) generally mean that we would need to |
26 |
> s/DEPEND/HDEPEND/ for the vast majority of ebuilds (ie all the |
27 |
> trivial ones)? |
28 |
> |
29 |
> That does effectively refer to the common depends as well. You |
30 |
> know, in the real world where there is no magical variables which |
31 |
> do miracles behind your back. |
32 |
> |
33 |
|
34 |
RDEPEND is defined in an earlier post (by Zac i think?) as target |
35 |
build+run dependencies; there are very few actual target build-only |
36 |
dependencies (ie, deps that need to be installed on the target and |
37 |
don't need to be installed on the host, and don't need to be on the |
38 |
target after build time). As such, HDEPEND since it means build-host |
39 |
build-time deps will still need to have these common dependencies |
40 |
specified but that doesn't have anything to do with the target's |
41 |
requirements, which right now are already entirely covered by RDEPEND |
42 |
(and not DEPEND) at all. |
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v2.0.19 (GNU/Linux) |
45 |
|
46 |
iF4EAREIAAYFAlBKTg0ACgkQ2ugaI38ACPBZJwD9E9MT2ZVsKtY+VujuMYjhi5EC |
47 |
B0RfyRnpXHu4JraBh+0A/014AWaOO3x70axEfdzTFbygRepDe6LWPqFy71nxBC3v |
48 |
=7hsL |
49 |
-----END PGP SIGNATURE----- |