1 |
Ciaran McCreesh wrote: |
2 |
> On Mon, 18 Dec 2006 07:28:25 +0000 Steve Long wrote: |
3 |
> | Ciaran McCreesh wrote: |
4 |
> | > That one pulls us back into the lack of distinction between "stuff |
5 |
> | > needed when compiling against this library" and "stuff this library |
6 |
> | > needs to run". |
7 |
> | |
8 |
> | Wouldn't your c-toolchain or a compiler eg for PERL or Java do? |
9 |
> |
10 |
> You're missing the distinction. The easy example, but not the best, is |
11 |
> pkg-config: many libraries must be used via pkg-config, so they need to |
12 |
> RDEPEND upon it to avoid breaking binary packages. However, they don't |
13 |
> actually require it at runtime. The other option, which is just about |
14 |
> doable in this one particular case, is to make any package that uses a |
15 |
> library that uses pkg-config DEPEND upon pkg-config. |
16 |
> |
17 |
What do you mean by "stuff needed when compiling against this library"? I'm |
18 |
not understanding what distinction you're trying to make- a reverse-compile |
19 |
dep? I can understand compile-time dependencies and run-time dependencies. |
20 |
You seem to be talking about the compile-time dependency of any pkg |
21 |
compiling against a library. Doh! I see what you mean, that isn't the same; |
22 |
so effectively there's another type of dep. |
23 |
|
24 |
How serious an issue is it in terms of deps on sys pkgs? |
25 |
|
26 |
> | > DEPEND="virtual/c-toolchain" would indeed be nice, but it's a rather |
27 |
> | > large change... |
28 |
> | > |
29 |
> | How so? Isn't it simply a new meta? |
30 |
> |
31 |
> And an entire tree to update before it becomes meaningful. |
32 |
> |
33 |
Sure, but the changes can propagate thru as people update their ebuilds, no? |
34 |
|
35 |
-- |
36 |
gentoo-dev@g.o mailing list |