1 |
Brad Cowan wrote: |
2 |
> On Thu, 2004-05-13 at 00:13, Jon Portnoy wrote: |
3 |
> |
4 |
>>On Wed, May 12, 2004 at 10:55:37PM -0500, Andrew Gaffney wrote: |
5 |
>> |
6 |
>>>Jon Portnoy wrote: |
7 |
>>> |
8 |
>>>>On Wed, May 12, 2004 at 10:27:48PM -0500, Andrew Gaffney wrote: |
9 |
>>>> |
10 |
>>>> |
11 |
>>>>>I was wondering why there was the separation between the compile-time |
12 |
>>>>>depends (DEPEND) and the run-time depends (RDEPEND). Aren't all of them |
13 |
>>>>>needed in order to run the program? Is there a practical reason for |
14 |
>>>>>splitting them up? |
15 |
>>>> |
16 |
>>>>DEPEND is for *building* the package; consider binary packages. |
17 |
>>> |
18 |
>>>Yes, but run-time dependencies can be installed before the package itself. |
19 |
>>>I still don't see a reason for splitting them up. |
20 |
>>> |
21 |
>> |
22 |
>>Because you don't want to include build-time dependencies when you |
23 |
>>distribute the binary package. |
24 |
> |
25 |
> Here's an example if you're not totally clear on what Jon is saying ( |
26 |
> which is 100% correct BTW ). Pkgconfig is needed to build XFce, but not |
27 |
> needed to run it (a DEPEND, not an RDEPEND), so there is no need to |
28 |
> include or install pkgconfig from the GRP set as it would just take up |
29 |
> precious space/bloat on the cd's and the binary user's computer/HD. |
30 |
> This also comes into play with reverse deps and depclean. How would you |
31 |
> be able to track what packages were no longer needed at runtime without |
32 |
> discriminating between the two? This leads to a much cleaner secure |
33 |
> system. |
34 |
|
35 |
That makes a lot more sense. Thanks for the clarification. |
36 |
|
37 |
-- |
38 |
Andrew Gaffney |
39 |
Network Administrator |
40 |
Skyline Aeronautics, LLC. |
41 |
636-357-1548 |
42 |
|
43 |
|
44 |
-- |
45 |
gentoo-dev@g.o mailing list |