Hi Andre,
Andre Fischer schrieb:
On 22.03.2012 21:46, TJ Frazier wrote:
On 3/22/2012 16:28, Rob Weir wrote:
On Thu, Mar 22, 2012 at 4:18 PM, Juergen Schmidt
<[email protected]> wrote:
On Thursday, 22. March 2012 at 15:19, Oliver-Rainer Wittmann wrote:
Hi,
On 22.03.2012 13:51, Herbert Duerr wrote:
Please note that the install sets that fall out of a build have
been renamed
from OOo* to Apache_OpenOffice_incubating* so that e.g.
OOo_3.4.0_MacOS_x86_install_en-US.dmg
now has the file name
Apache_OpenOffice_incubating_3.4.0_MacOS_x86_install_en-US.dmg
I would prefer a shorter AOO_incubating_3.4.0_...
I used for example a scheme like aoo-3.4-incubating-src... for our
source release. Similar to for example the odftoolkit (incubating)
project.
Why expanding OOo to Apache_OpenOffice_? Ok it seems we have to
include "incubating" but that's it.
It looks like the recommendation is to use the full product name, but
the "Apache" part is optional for podlings.
So "openoffice-3.4.0-incubating" would be one possible root.
See: http://incubator.apache.org/guides/releasemanagement.html#naming
Has anybody checked to see if we'll run into that idiotic 72-character
limitation on path names?
Can you explain where there this a 72-character limitation ?
It is in https://issues.apache.org/ooo/show_bug.cgi?id=118823. I saw the
problem with an administrative installation. The installation itself
runs through, but the program cannot be started.
For example an installation with path
D:\SoftwareArchiv\OpenOffice.orgDownload\AOOr129test\lauffertig\program
or with path
D:\SoftwareArchiv\OpenOffice.orgDownload\AOO dev r1296433\program
works, but an installation with path
D:\SoftwareArchiv\OpenOffice.orgDownload\AOO_dev_r129test\lauffertig\program
does not work.
As far as I know Jürgen Schmidt has done some tests too.
Kind regards
Regina
