On Tuesday, September 01, 2015 6:06:05 PM walt wrote: > This is on my one amd64 (stable) machine, so the following proposed > update should be safe and Just Work(TM), right? > > Maybe it will, but there is no way I'm going to let this upgrade happen > tonight when I'm tired from fighting all day with the so-called 'stable' > computers at work: > > Calculating dependencies... done! > [ebuild U ] sys-libs/ncurses-5.9-r5 [5.9-r3] > [ebuild NS ] sys-libs/ncurses-5.9-r99 [5.9-r3] USE="cxx gpm unicode > -ada -static-libs -tinfo" ABI_X86="32 (64) (-x32)" > > Is this going to install two different (slotted) versions of ncurses-5.9 > on my stable machine? > > If not, then this proposed update must be an experiment or a hack or a > workaround of some kind. On my *stable* machine! > > Can you tell I'm in a bad mood and a bit paranoid at the moment? I'm > going to bed and will update the stable machine again in the morning. > Hrmph! > >
It has something to do with the slot move. It is safe to install, I installed that one about a week ago. I don't fully understand it, but I think it's to cause the 6.0 update to come before the 5.9-r101 so that you don't go through what I went through yesterday when I tried to outsmart portage (when you do the slot move from r5 to r101 it tries to preserve the old libraries so it collides with itself). -- Fernando Rodriguez
