| 1 |
On 27 November 2017 at 20:44, Michael Orlitzky <mjo@g.o> wrote: |
| 2 |
|
| 3 |
> On 11/27/2017 03:37 PM, Arve Barsnes wrote: |
| 4 |
> > |
| 5 |
> > Sounds kind of weird? If he has keyworded the game package, shouldn't it |
| 6 |
> > just never install that version if it depends on an unstable package? |
| 7 |
> |
| 8 |
> That's right, but if there are two available ~arch versions, one of |
| 9 |
> which has all stable dependencies and (the newer) one of which has all |
| 10 |
> ~arch dependencies, then portage will try to install the newer one and |
| 11 |
> tell you to keyword a million things -- even though it could install the |
| 12 |
> first one with less hassle. |
| 13 |
> |
| 14 |
> Ah, hadn't thought of that scenario. Reading the emerge man pages, I would |
| 15 |
try the --autounmask-keep-masks option, but emerge might never consider |
| 16 |
anything but the latest stable version either way. |
Archives