Issue 109096

Summary:	Problems with extensions and long paths on windows
Product:	General	Reporter:	mikhail.voytenko
Component:	code	Assignee:	Olaf Felka <olaf-openoffice>
Status:	CLOSED FIXED	QA Contact:	issues@framework <issues>
Severity:	Trivial
Priority:	P3	CC:	issues, joachim.lingner, mikhail.voytenko
Version:	DEV300m69
Target Milestone:	3.4.0
Hardware:	PC (x86_64)
OS:	Windows, all
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description mikhail.voytenko 2010-02-10 07:44:25 UTC

This issue is a successor of issue 50885.

Berkeley DB does not support long paths on Windows, so the problem has to be
workarounded in our source code before we can get rid of Berkeley DB completely.
A possible workaround could be to copy the database file to a temporary file,
edit it, and then copy back.

Comment 1 joachim.lingner 2010-02-10 11:47:53 UTC

Comment 2 joachim.lingner 2010-06-04 06:22:30 UTC

Retargeted to 3.4

Comment 3 joachim.lingner 2011-03-03 10:56:52 UTC

Changed the summary because the berkeley db is not affected but there were several other places which caused errors. Problems occurred during building using the PKGFORMAT=installed or PKGFORMAT=archived. Then the path to the installation folder of the extensions and the user installation could exceed 260 characters which lead to problems when running unopkg sync at the end of the installation. This could be workarounded by setting LOCALINSTALLDIR, so that the path length is shorter.

The other scenario is when the path to the user installation is very long. For example on windows XP:
c:\documents and settings\users\i have a very long name ....
Within the user installation the path to extensions and registration data can also be quiet long, so when adding theses two the overall length is greater 260 chars.

Comment 4 joachim.lingner 2011-03-03 12:16:48 UTC

cygwin cannot start soffice or unopkg when its path is longer than 260 chars. However, the fix helps when data are accessed during unopkg sync. For example. <long_path>/office/share/prereg/bundled/registry/com.sun.star.comp.deployment.configuration.packageregistrybackend/sva4m5ri.tmp/somexcufilefromanextension.xcu

Comment 5 joachim.lingner 2011-03-04 12:28:52 UTC

Comment 6 joachim.lingner 2011-03-04 13:30:54 UTC

Comment 7 joachim.lingner 2011-03-04 13:36:05 UTC

@of: Please test Windows XP and Windows7. 
Create a user installation at a location where the path is very long (>260). Redirect the user installation in the boostrap.ini.
On XP you need cygwin to create paths longer than 260 characters.
Install several extensions (user) and test if they work.
Please have also a look at the help and the extension help (for example weblog publisher), because I touched code which is used for help creation.

Comment 8 Olaf Felka 2011-03-09 12:51:59 UTC

of: Looks good in cws jl164.