| 1 |
John H. Moe writes: |
| 2 |
|
| 3 |
> Alex Schuster wrote: |
| 4 |
> > Roy Wright writes: |
| 5 |
|
| 6 |
> >> 4) recustomize kde as the ~/.kde will not be migrated |
| 7 |
> > |
| 8 |
> > I really hope I can just copy .kde4.2 to .kde4 and all (okay, most) |
| 9 |
> > settings will be kept. I think it just _should_ work. Customizing all |
| 10 |
> > over again every time a new KDE arrives would be no good. |
| 11 |
|
| 12 |
> Well, I don't know about necessary, but on my box, when I tried to |
| 13 |
> update from kde-meta:4.2 to kde-meta:4.3, there were a few blockers that |
| 14 |
> wouldn't let it go through, so I ended up unmerging 4.2, then emerging |
| 15 |
> 4.3 (which took about 4-6 hours, but I have distcc set up between two |
| 16 |
> boxes, so that probably sped things up). However, I seem to remember |
| 17 |
> that the blockers were with PyQt, Python and eselect-python; I hadn't |
| 18 |
> thought about it, cause I'm still not THAT experienced with Linux in |
| 19 |
> general, and Gentoo in particular, but the Python update was a Big Deal, |
| 20 |
> so perhaps updating Python before the KDE upgrade would have been a good |
| 21 |
> idea. :-P Granted though, I didn't use sets, so it may be a bit |
| 22 |
> different for you. |
| 23 |
|
| 24 |
Yes, emerge -p @kde-4.3 shows now problems. Maybe it's because of using |
| 25 |
sets, or I already have resolved the blockers, as I already had trouble with |
| 26 |
PyQt and such. |
| 27 |
|
| 28 |
> Oh, and I didn't touch my .kde or .kde4 folders during this process, and |
| 29 |
> as far as I can tell, it's still using all of my customizations... |
| 30 |
|
| 31 |
This sounds good. |
| 32 |
|
| 33 |
Wonko |
Archives