1 |
On 11/27/2017 03:37 PM, Arve Barsnes wrote: |
2 |
> |
3 |
> Sounds kind of weird? If he has keyworded the game package, shouldn't it |
4 |
> just never install that version if it depends on an unstable package? |
5 |
|
6 |
That's right, but if there are two available ~arch versions, one of |
7 |
which has all stable dependencies and (the newer) one of which has all |
8 |
~arch dependencies, then portage will try to install the newer one and |
9 |
tell you to keyword a million things -- even though it could install the |
10 |
first one with less hassle. |
11 |
|
12 |
For example, if you're on a system with no ruby packages, then it's the |
13 |
difference between having to keyword 10 packages for rails-x.y.z versus |
14 |
200 packages for rails-x.y.(z+1). I'd rather have the slightly older |
15 |
version that requires less configuration. |