1 |
On Thursday 10 April 2008, 12:56, Alan McKinnon wrote: |
2 |
|
3 |
> > This is not sensible. If Uwe says "A blocks B", it means that A is |
4 |
> > getting in the way of B, not the other way around. |
5 |
> |
6 |
> No, that's incorrect. I think you are attaching an incorrect meaning |
7 |
> to the output wording. |
8 |
> |
9 |
> In this case, A's ebuild DEPENDs on !B |
10 |
> |
11 |
> The error output has to come from A's ebuild as that is where the |
12 |
> block comes from, and the standard wording is "A blocks B" as in: A's |
13 |
> ebuild says it cannot be merged if B is already there. |
14 |
|
15 |
I'm no native speaker, but I'd call whay you describe "B blocks A", not |
16 |
viceversa. |
17 |
|
18 |
> B does not block A as B's ebuild did not know about A when it was |
19 |
> written. B does nto have a problem with A, instead A knows it has a |
20 |
> problem with B. You should read "block" in emerge output as a synonym |
21 |
> for "incompatible with" rather than "gets in the way of" as you appear |
22 |
> to be doing. |
23 |
|
24 |
If the word in emerge output was "block", meaning generically "there is a |
25 |
block, an incompatibility" you would be correct. But that word |
26 |
is "blocks", 3rd person singular, implying a subject and an object, ie |
27 |
something blocks something else. Or, at least that's how I see that, and |
28 |
I may be wrong of course. |
29 |
-- |
30 |
gentoo-user@l.g.o mailing list |