1 |
Dale posted on Wed, 08 Dec 2010 23:21:53 -0600 as excerpted: |
2 |
|
3 |
> Alex Schuster wrote: |
4 |
|
5 |
>> If you are running databases like mysql, you need to export the |
6 |
>> databases and import them later. This is because they are in binary |
7 |
>> format, and the datatypes are different in x86 and amd64 world. |
8 |
|
9 |
> I don't have anything that I generated anyway. I have something |
10 |
> installed that KDE pulled in if I recall correctly. I'll let KDE start |
11 |
> off fresh tho. |
12 |
> |
13 |
> This does bring me to another thought tho. Would I be able to copy my |
14 |
> /home directory over from a x86 system? I'm thinking I would but want |
15 |
> to make sure. |
16 |
|
17 |
In general, the same /home should be fine, 32-bit or 64-bit. |
18 |
|
19 |
However, kde4 uses a database for akonadi. With older versions (thru 4.3 |
20 |
at least), it was mysql by default. Newer versions (from 4.5) use sqlite |
21 |
by default, tho there can be a bit of an issue trying to upgrade as the |
22 |
ebuild tries to default to sqlite, but the user config is still set to |
23 |
mysql. If mysql is still on the system, it'll use it since that's what |
24 |
was (automatically) configured in user settings, but if it's cleaned off |
25 |
as a now unneeded dependency, akonadi would of course fail, until the |
26 |
user's configure is (manually) updated. Of course, new-installs or new- |
27 |
users wouldn't have the issue as they'd not have that bit of existing |
28 |
config. I don't recall for sure whether it was 4.4 or 4.5 that switched, |
29 |
thus the gap above, but the sqlite dependency is FAR easier to deal with, |
30 |
now that they've worked thru the threading issues or whatever it was that |
31 |
was blocking its use earlier. |
32 |
|
33 |
I wasn't aware of a 32/64 mysql database incompatibility, but assuming |
34 |
Alex is correct, you might experience issues with that mysql/akonadi |
35 |
dependency, if you're still using an older kde or if you migrate the same |
36 |
home (with the mysql config) over. But as long as you either don't use |
37 |
akonadi (with 4.4/4.5 it's used for the address book but not for kmail |
38 |
itself; I don't know about kopete/etc as I don't do IRC/IM), or already |
39 |
have it configured for the sqlite backend, and aren't using mysql for |
40 |
anything else, you should be fine. |
41 |
|
42 |
And even in the event that you're still using the mysql backend, at worst, |
43 |
akonadi only caches the data before its written to traditional text files, |
44 |
so any loss of data should be only what didn't get written back to the |
45 |
permanent storage. tho of course it might not be working for a bit as you |
46 |
get the config squared away. |
47 |
|
48 |
Basically, then, as from what I recall you're following newer kde, 4.5.x, |
49 |
and not waiting for full Gentoo stabilization, I'd ensure that you're |
50 |
using the sqlite backend, not mysql, before you copy your home dir over, |
51 |
and then you should be fine. |
52 |
|
53 |
-- |
54 |
Duncan - List replies preferred. No HTML msgs. |
55 |
"Every nonfree program has a lord, a master -- |
56 |
and if you use the program, he is your master." Richard Stallman |