| 1 |
On 27 November 2017 at 20:34, Rich Freeman <rich0@g.o> wrote: |
| 2 |
|
| 3 |
> To answer his question, there is not any way out-of-the-box to tell |
| 4 |
> portage to install the latest ~arch version of a package that has only |
| 5 |
> stable or already-accepted dependencies. Certainly it should be |
| 6 |
> possible to build such a feature, but it doesn't exist today. |
| 7 |
> |
| 8 |
|
| 9 |
Sounds kind of weird? If he has keyworded the game package, shouldn't it |
| 10 |
just never install that version if it depends on an unstable package? I |
| 11 |
know I've seen errors of that kind on a machine running stable, but |
| 12 |
shouldn't emerge just skip the package update if you can't satisfy its |
| 13 |
dependencies? In my head it sounds like that should be something of a |
| 14 |
default, but maybe I'm missing something. |
Archives