[Libreoffice-qa] Extension migration to LO 4 (was: minutes of ESC call ...)

[Stephan Bergmann]

On 11/14/2012 09:07 AM, Stephan Bergmann wrote:
> On 10/17/2012 01:14 PM, Michael Meeks wrote:
>> * 4.0 plans / naming / ABI stability etc. (Kendy)
>>     + user-installs labelled with '4'
>>         + migration code to do a one-shot config / setup fix.
>>         + can loose old back-compat code.
>>         + we get the berkeleydb removal as part of re-basing.
>
> BTW, did anybody look into that berkeleydb removal code, regarding its
> ability to migrate from existing user profiles (as berkeleydb files are
> used in the user profile to keep track of installed extensions)?

So migration of per-user installed extensions from a pre-4 user profile 
to LO 4 appears to work fine now after 
<http://cgit.freedesktop.org/libreoffice/core/commit/?id=bd9c4510ff13ab7e935ed12c5b6d1f132c6f2b79> 
"Take extra cache/uno_packages/*.tmp_/*properties files into account," 
even filtering out those blacklisted via 
/org.openoffice.Setup/MigrationStep/ExcludedExtensions, with one exception:

Per-user installed extensions that had been explicitly disabled in the 
old user profile are enabled in LO 4.

To put that into perspective, the fix for 
<https://bugs.freedesktop.org/show_bug.cgi?id=32263> "Config file 
location" (first appearing in LO 3.5.0?) that required "migration" of 
user profiles from ~/.libreoffice/3 to ~/.config/libreoffice/3 on Linux 
appears to have had that defect too, in addition to the more severe 
defect of erratically not migrating some per-user installed extensions 
at all thanks to the problem now addressed with 
bd9c4510ff13ab7e935ed12c5b6d1f132c6f2b79 -- at least, that's my 
observation when trying to re-enact that "migration" with a current 
libreoffice-3-6 build.

And I see no cheap way to fix that, and am not sure it would be worth it 
to try hard.

(This sounds similar to 
<https://bugs.freedesktop.org/show_bug.cgi?id=57224> "CONFIGURATION: 
Deactivated Extensions become active" but is rather unrelated 
technically.  That issue is strictly about upgrades within a LO 3.x or 
LO 4.x series.)

Stephan