Re: [dev] Long paths on Windows

2008-04-11 Thread Stephan Bergmann

Oliver Brinzing wrote:

Hi,

a short question's regarding path's:

Is it generally a good idea to have space's and the version number
(for example OOo-dev 3.0,  Basis 3.0,...) inside the oo install 
path's ?


spaces: no idea if that is good or bad; when coming up with Basis 3.0 
I just followed prior art (OpenOffice.org 2.4)


version number: see What shall be the paths where the tree layers are 
installed, and is it necessary to encode any version numbers in those 
paths? in 
http://wiki.services.openoffice.org/wiki/ODF_Toolkit/Efforts/Three-Layer_OOo


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Long paths on Windows

2008-04-11 Thread Oliver Brinzing

Hi,

spaces: no idea if that is good or bad; when coming up with Basis 3.0 
I just followed prior art (OpenOffice.org 2.4)


that's true, but till oo 2.4 one had a chance to install to a path
without spaces and version numbering, like c:\programs\openoffice.
that's not possible anymore ...

Oliver

--

GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45



signature.asc
Description: OpenPGP digital signature


Re: [dev] Long paths on Windows

2008-04-11 Thread Stephan Bergmann

Oliver Brinzing wrote:

Hi,

spaces: no idea if that is good or bad; when coming up with Basis 
3.0 I just followed prior art (OpenOffice.org 2.4)


that's true, but till oo 2.4 one had a chance to install to a path
without spaces and version numbering, like c:\programs\openoffice.
that's not possible anymore ...


Right.

I'm rather indifferent about the exact naming details (apart from the 
technically-imposed version numbers encoded in file names, of course), 
maybe other people want to give input.


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Long paths on Windows

2008-04-11 Thread Stephan Bergmann

Stephan Bergmann wrote:
Applications on Windows are notorious for having problems with long file 
system paths.  Some expert on Windows can probably give more insight 
into the topic in general.  For OOo, the situation has always been that 
it can start to fail in mysterious ways if the installation path or the 
user installation path is too long (whatever too long is exactly). 
Since DEV300m4, the situation has become slightly worse, in that too 
long has apparently become a little shorter:


- For one, since OOo is now in three layers where the upper layers need 
to create paths to the lower ones, on Windows there is now a function 
(resolveLink, desktop/win32/source/extendloaderenvironment.cxx:1.4, l. 
115 ff) to create a new path from an absolute path and a text file 
containing a relative path.  The text file (basis-link resp. ure-link) 
typically contains a relative path starting with one or more .. 
segments, but resolveLink does not bother to remove these from the 
resulting new path.  That is, instead of the path


  C:\Program Files\OpenOffice.org\Basis 3.0\program

you get the path

  C:\Program Files\OpenOffice.org 3.0\..\OpenOffice.org\Basis 3.0\program

which is somewhat longer.  I will see to improve resolveLink in one of 
the next milestone builds.


see http://www.openoffice.org/issues/show_bug.cgi?id=88166

-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Long paths on Windows

2008-04-10 Thread Oliver Brinzing

Hi,

a short question's regarding path's:

Is it generally a good idea to have space's and the version number
(for example OOo-dev 3.0,  Basis 3.0,...) inside the oo install path's ?

This can be a trouble source too, if one needs to do installation using simple 
batch scripts ...

Oliver


GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45



signature.asc
Description: OpenPGP digital signature


[dev] Long paths on Windows

2008-04-09 Thread Stephan Bergmann
Applications on Windows are notorious for having problems with long file 
system paths.  Some expert on Windows can probably give more insight 
into the topic in general.  For OOo, the situation has always been that 
it can start to fail in mysterious ways if the installation path or the 
user installation path is too long (whatever too long is exactly). 
Since DEV300m4, the situation has become slightly worse, in that too 
long has apparently become a little shorter:


- For one, since OOo is now in three layers where the upper layers need 
to create paths to the lower ones, on Windows there is now a function 
(resolveLink, desktop/win32/source/extendloaderenvironment.cxx:1.4, l. 
115 ff) to create a new path from an absolute path and a text file 
containing a relative path.  The text file (basis-link resp. ure-link) 
typically contains a relative path starting with one or more .. 
segments, but resolveLink does not bother to remove these from the 
resulting new path.  That is, instead of the path


  C:\Program Files\OpenOffice.org\Basis 3.0\program

you get the path

  C:\Program Files\OpenOffice.org 3.0\..\OpenOffice.org\Basis 3.0\program

which is somewhat longer.  I will see to improve resolveLink in one of 
the next milestone builds.


- For another, at least so called administrative installations 
(msiexec /a) let you chose an installation path (other than C:\Program 
Files), and in older versions the chosen path replaced part of the 
prefix of an OOo's installation path.  That is, if you chose D:\Foo as 
installation path, for example the OOo 2.4 soffice.exe ended up at


  D:\Foo\program\soffice.exe

(the OpenOffice.org 2.4 segment of the corresponding default

  C:\Program Files\OpenOffice.org 2.4\program\soffice.exe

was dropped).  However, since we now install three adjacent trees 
instead of just one, we can no longer drop the OpenOffice.org 3.0 
segment, so if you now chose D:\Foo as installation path, soffice.exe 
ends up at the path


  D:\Foo\OpenOffice.org 3.0\program\soffice.exe

which is somewhat longer.

In short:  If your OOo installation on Windows behaves strange, maybe 
you should install it into a shorter path.  :(


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Long paths on Windows

2008-04-09 Thread Cor Nouws

Hi Stephan,

Stephan Bergmann wrote (9-4-2008 11:47)


[...]
In short:  If your OOo installation on Windows behaves strange, maybe 
you should install it into a shorter path.  :(


My OOo installation will suffer less than my OpenOffice.org 
installation. (hint).


Regards,
Cor

--

The Year of 3 -2008- Het jaar van 3

Cor Nouws
Arnhem - Netherlands - nl.OpenOffice.org - marketing contact


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]