Apache OpenOffice (AOO) Bugzilla – Issue 75637
During installation (first launch) of OOo 2.1, the existing settings of OOo 2.0 are not migrated
Last modified: 2007-05-27 12:49:36 UTC
During installation (first launch) of OOo 2.1, the existing settings of OOo 2.0 (in ~/.openoffice.org2/user) are not migrated to the new location in ~/ Library/Application\ Support/OpenOffice.org\ 2.1/user. This results in major pain like reconfiguring and, worst of all, the user wordbook is "lost" for the average user. Expected result: non-conflicting settings are copied over from old profile location. For future upgrade paths, http://qa.openoffice.org/issues/show_bug.cgi?id=73224 is the solution. But IMHO, a safe upgrade for 2.0 users should be possible, too. (and I hope 2.2 does it right, haven't checked yet as there is no German RC to be found)
What about simply rename the old folder ? BTW, we will change soon for : ~/Library/Application Support/OpenOffice.org2
2.2rc3 can be found at: ftp://ooopackages.good-day.net:21/pub/OpenOffice.org/MacOSX/2.2.0rc3_20070306/ Actually it will be ~/Library/Application Support/OpenOffice.org/2/ That we will be moving to soon. This will mean that there will be no data loss until OpenOffice.org 3, when there will probably be a settings migration again.
re c#1: Of course I migrated the data by hand. This is not about people who know what they are doing though, but about end users. Try to explain this to an average Mac user. They won't even _find_ the old folder as it is hidden in the Finder. re c#2: Thanks, will try these. But as I understand comment 1, situation has probably not changed in 2.2. In general: "There will be no dataloss until..." - there shouldn't be any dataloss at all. Never. just my 2ct.
ericb-> mmx2000 First, to open a hidden dir, you can do : 1) Apple + TAB , select the Finder 2) Apple key + Shift + G and type : ~/.openoffice.org2 ... and copy everything inside the new created ~/Library/Application Support/OpenOffice.org 2.x Second, what about use a shell script for the renaming ? something like ( untested) : #!/bin/bash cp -r ~/.openoffice.org2 ~/Library/Application Support/OpenOffice.org\ 2.x ...should do it. Then choose a name ( like rename.command) , chmod, put it on the Desktop, and execute it using a double click. HTH
you don't seem to understand. It's not about me not knowing how to do it. But how do you expect e.g. your grandmother to upgrade? Make her redo all the settings and reinstall the additional dictionaries? Let her go through all the pain of retraining the wordbook the words that are not in the dictionary?
ericb->mmx2000 Sure I understand : Yes, the naming was a bad idea, and we fixed that. But this change cannot be made instantaneously. FYI, our resources are mainly used for Aqua version ( without X11, alpha version coming soon ) and we had to make choices. Now, please don't forget we are volunteers, (means not paid, and working in our free time, after real work), and you use OpenOffice.org for free... Last but not least, if you have a solution, or a patch to fix that, or want to do a donation (please have a look at my blog http://eric.bachard.free.fr/news ) ... you are welcome :)
OK, so maybe it's too late for 2.2 anyway. But please keep this in mind and implement some migration tool for any future version that changes the profile path yet again. E.g. Firefox migrated at some point from ~/Library/Firefox to ~/Library/Application Support/Firefox. They used a Profile Migration Tool for that, so the user did not lose anything. And yes, I know you do this in your spare time. I myself am active in the Mozilla project and usually I do not get bitchy if I see that my point is at least understood. Unfortunately I currently lack both time and skill to implement such a migration tool myself - so I can't provide a patch for the time being. Thanks for everything and I am really looking forward to an Aqua version. (the old NeoOffice was way too slow on my machine) Greetings . . . Martin
I had created migration scripts into cws macosxversioning01, which eventually got into OOo 2.2. However, the migration part of it was dropped as: 1) there was not enough (time/resources for) quality testing and 2) for the reason that developers' desires were prioritized over users' desires: it was more important to be able to have many versions of OOo running at the same time, than getting the one version that users normally have, migrated. So if somebody feels like wanting to help normal users, have a look at the cws and its issue. I won't work on it anymore (Trying one time is enough).
ericb->mox The migration tool is a good idea, and I have put the point to be discussed on the next IRC meeting. If you don't want to work on that anymore, please propose on mac@porting mailing list, and someone else will take the task over. Thank you
ericb: As it was discussed on Mac port meeting and since I already said I'm not working on this, this is the last thing you'll hear from me relating to this issue.
.
1) no news since a long time 2) a solution does exist closing as wontfix
closing