On 03/25/2018 05:10:29 PM, Ian Zimmerman wrote:
On 2018-03-25 13:50, Neil Bothwick wrote:
> The only hard block here appears to be xscrnsaverproto, unmerge
that and
> the rest should take care of themselves. I had all the soft blocks
today
> but not that one, and everything worked fine.
But ... I actually have packages that depend on scrnsaverproto:
So I have to unmerge xautolock and xssstate too? That will be painful
because they're baked deep into my X configuration. I think it will
require a trip to the Linux console :-P
No,
I have x11-base/xorg-proto-2018.4 and x11-proto/scrnsaverproto-1.2.2-r2
install here.
Try to emerge x11-base/xorg-proto and x11-proto/scrnsaverproto
simultaneously.
