Moin, in case you want to follow up to this mail, please reply to [EMAIL PROTECTED] as this is not a "developers only" topic!
As explained in the issue 94240 by Stephan Bergmann, wie have an incompatibility between "vanilla" Linux builds of OpenOffice.org and OOo versions of the Linux distributions that are linked against a system libbdb (Berkeley DB). AFAIK all distros use a system bdb library, but I know it at least for sure for Ubuntu where we discovered the problem. The bundled bdb library has an older version and it can't read the files created by the possibly newer version of the Linux distribution. The result is that any vanilla version that is installed after the distro version has been run can't read the UNO packages database files in the user profile. So people that try out an OOo3 RC build and select "migration of personal data" will get a "defective" UNO packages database as the RC version can't read the data that has been migrated from the user profile created by the distro OOo2 version. The same happens if a vanilla build is installed and reuses (not migrates) the existing user profile created by a distro version. Depending on how and when the first access to the extension layer happens in the execution flow, OOo at least won't see any installed extensions and can't install any new ones, but it's also very likely it will crash due to an uncaught runtime exception. In fact the latter happens with the migrated RC builds, we got a lot of crash reports that showed us this problem. Let's put aside the migration thing, how shall we proceed in general? Shall we - not try to fix the problem and just prevent the crash, but then extensions won't run in case of a switch distro->vanilla and users must remove the uno_packages manually? - create different user profiles for vanilla and other OOo builds? - don't bundle libbdb in vanilla builds anymore and make this library a system requirement on Linux? I wanted to present this problem to a larger audience of people that are working on OOo builds and releases and the releases list comes closest to that (dev list is on cc). If you know other lists or people to get involved, please forward. I would prefer the last option but I assume that for 3.0 it's perhaps too late so that we must choose one of the other options. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
