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