You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by Pedro Lino <pe...@gmail.com> on 2014/06/09 18:19:52 UTC

Using dailies under Windows

Hi all

I'm currently running build AOO420m1(Build:9800)  -  Rev. 1596566 and
wanted to update to build 1600883 (under Windows XP Pro x86 en_US SP3).

Unfortunately the installer tells me that "The same version of this product
is already installed" and the only option is to Finish installation.

Isn't it possible to allow the installer to detect the build version or to
allow to install the same version of AOO as a Repair install?

Thanks,
Pedro

Re: Using dailies under Windows

Posted by Pedro Lino <pe...@gmail.com>.
Hi Andrea, all

That option was suggested before on this "thread". But that is exactly what
I want to avoid. Parallel dailies take up a lot of disk space and they
don't make any sense unless you are looking for a regression on a specific
date...
I'm requesting the exact opposite: that testers can install dailies as
their *only* production copy. I believe this is the most accurate use of
daily builds (unlike LibreOffice which forces dailies and Betas to a
*similar* installation to a LibreOfficeDev path and settings folder)

This allows to detect bugs in the real installation much earlier in
production.

Cheers,
Pedro


On Sat, Jun 21, 2014 at 10:15 PM, Andrea Pescetti <pe...@apache.org>
wrote:

> On 12/06/2014 Pedro Lino wrote:
>
>> But this is not what I meant... Since AOO dailies install to the standard
>> path and use the default profile, a tester can use it as the main (and
>> only) installation
>>
>
> It's not very user friendly, but "msiexec /a" (or "setup /a") should allow
> you to install a Windows build where you wish. See
> https://wiki.openoffice.org/wiki/Run_OOo_versions_parallel
> and if it works for you with 4.x ask for a wiki account here on the list
> (or the dev list), so that you can update the page with your findings!
>
> Regards,
>   Andrea.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: qa-help@openoffice.apache.org
>
>

Re: Using dailies under Windows

Posted by Andrea Pescetti <pe...@apache.org>.
On 12/06/2014 Pedro Lino wrote:
> But this is not what I meant... Since AOO dailies install to the standard
> path and use the default profile, a tester can use it as the main (and
> only) installation

It's not very user friendly, but "msiexec /a" (or "setup /a") should 
allow you to install a Windows build where you wish. See
https://wiki.openoffice.org/wiki/Run_OOo_versions_parallel
and if it works for you with 4.x ask for a wiki account here on the list 
(or the dev list), so that you can update the page with your findings!

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: Using dailies under Windows

Posted by Pedro Lino <pe...@gmail.com>.
Hi Stuart

Thank you for the extensive instructions. Actually I could use Florian
Reisinger's SI GUI do to all of this... But I really don't want to have
several parallel install folders. Actually I think it doesn't makes sense
unless someone is looking for a particular regression between two daily
builds.

But this is not what I meant... Since AOO dailies install to the standard
path and use the default profile, a tester can use it as the main (and
only) installation (unlike LO dailies which install in separate folder and
forcibly create a separate profile)

The only step preventing from installing consecutive dailies is that the
installer detects that a version with the same release is installed. If the
build number could be taken into account, it would allow testers to easily
update to the latest nightly without having to uninstall first.

I'm asking the AOO devs to please consider this as a courtesy to people
testing dailies/nightlies.

Thanks,
Pedro


On Thu, Jun 12, 2014 at 8:50 PM, V Stuart Foote <VS...@utsa.edu>
wrote:

> Pedro, *,
>
> Short of uninstalling and installing cleanly each time, these buildbot
>  nightly versions do not clean up after themselves.
>
> Using Microsoft's package installer -- msiexec.exe offers a reasonable
> work around of the /A Administrative, aka Server install, and running
> multiple versions in parallel.
>
> So with the nightly build downloaded, you can use any unzip program to
> extract the whole package into a folder.
>
> And then run the  Microsoft installer in  /A administrative mode.
>
> But, this does not "register" the the program as an application in the
> Windows registry. And, unless changed, the default user profile will
> conflict.  So, instead you can do a bit more tweaking of the /A
> installation, to be able to isolate each instance of it.
>
> That is done by installing to a unique location with at TARGETDIR flag,
> and then editing the bootstrap.ini to make the user profile relative to the
> installation.  E.g. the steps to install:
>
> 1.) Download a current nightly build,
> Apache_OpenOffice_4.2.0_Win_x86_install_en-US_1601656.exe
> 2.) unzip the package (rather than running it) into a folder--the name is
> not important, but good practice to not include spaces.
> 3.) open a command window (cmd.exe) and cd into the folder
> 4.) issue the command  "msiexec.exe /A openoffice420.msi /L*v
> AOO420_r1601656.log TARGETDIR="C:\AOO_420_r1601656"   -- note the quotes
> after the TARGETDIR=
> 5.) the Microsoft installer will perform the /A administrative install,
> writing a verbose log in the current folder, and creating a new directory
> C:\AOO_420_r1601656 -- you can review the log should there be any issues
> 6.) change directory into that new folder
> 7.) and from there change to the C:\AOO_420_r1601656\program folder
> 8.) make a backup of the bootstrap.ini file, and then edit the original
> 9.) locate the line that reads:
> UserInstallation=$SYSUSERCONFIG/OpenOffice/4
> 10.) delete the  "$SYSUSERCONFIG" and replace it with "$ORIGIN/.." this
> moves the  user configuration to a path relative to this installation, and
> other than the $SYSUSERCONFIG the OpenOffice/4 can be changed or left as
> is--personally I go with the suggested $ORIGIN/../Data/settings. Removing
> the SYSUSERCONFIG removes any conflict between versions.
> 11.) in the same C:\AOO_420_r1601656\program folder, any of the component
> launchers can be sent to the desktop to create a shortcut--but I usually
> only make one for the soffice.exe, and then from the desktop rename the
> shortcut to match the version -- AOO_420_r1601656 so I can keep track of it.
> 12.) launch the shortcut, the user profile and any
> registrymodifications.xcu configuration will be local to this /A install.
>
> When the next nightly build you'd like to work with is posted, simply
> repeat the process placing the install into a folder of its own.
>
> Stuart
>
>
>
>
>
> ________________________________________
> From: Pedro Lino <pe...@gmail.com>
> Sent: Thursday, June 12, 2014 2:08 PM
> To: qa@openoffice.apache.org
> Subject: Re: Using dailies under Windows
>
> Hi Ouchka
>
> msiexec / a openoffice400.msi.
> >
>
> This is essentially what I needed ;)
>
> I still think it would be nice if the installer detected that the build is
> newer and allowed to install without any "tricks". This would be more user
> friendly ;)
>
> Merci bien!
>
> Kind regards,
> Pedro
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: qa-help@openoffice.apache.org
>
>

RE: Using dailies under Windows

Posted by V Stuart Foote <VS...@utsa.edu>.
Pedro, *,

Short of uninstalling and installing cleanly each time, these buildbot  nightly versions do not clean up after themselves.

Using Microsoft's package installer -- msiexec.exe offers a reasonable work around of the /A Administrative, aka Server install, and running multiple versions in parallel.

So with the nightly build downloaded, you can use any unzip program to extract the whole package into a folder.

And then run the  Microsoft installer in  /A administrative mode.

But, this does not "register" the the program as an application in the Windows registry. And, unless changed, the default user profile will conflict.  So, instead you can do a bit more tweaking of the /A installation, to be able to isolate each instance of it.

That is done by installing to a unique location with at TARGETDIR flag, and then editing the bootstrap.ini to make the user profile relative to the installation.  E.g. the steps to install:

1.) Download a current nightly build, Apache_OpenOffice_4.2.0_Win_x86_install_en-US_1601656.exe
2.) unzip the package (rather than running it) into a folder--the name is not important, but good practice to not include spaces.
3.) open a command window (cmd.exe) and cd into the folder
4.) issue the command  "msiexec.exe /A openoffice420.msi /L*v AOO420_r1601656.log TARGETDIR="C:\AOO_420_r1601656"   -- note the quotes after the TARGETDIR=
5.) the Microsoft installer will perform the /A administrative install, writing a verbose log in the current folder, and creating a new directory C:\AOO_420_r1601656 -- you can review the log should there be any issues
6.) change directory into that new folder
7.) and from there change to the C:\AOO_420_r1601656\program folder
8.) make a backup of the bootstrap.ini file, and then edit the original
9.) locate the line that reads: UserInstallation=$SYSUSERCONFIG/OpenOffice/4
10.) delete the  "$SYSUSERCONFIG" and replace it with "$ORIGIN/.." this moves the  user configuration to a path relative to this installation, and other than the $SYSUSERCONFIG the OpenOffice/4 can be changed or left as is--personally I go with the suggested $ORIGIN/../Data/settings. Removing the SYSUSERCONFIG removes any conflict between versions.
11.) in the same C:\AOO_420_r1601656\program folder, any of the component launchers can be sent to the desktop to create a shortcut--but I usually only make one for the soffice.exe, and then from the desktop rename the shortcut to match the version -- AOO_420_r1601656 so I can keep track of it.
12.) launch the shortcut, the user profile and any registrymodifications.xcu configuration will be local to this /A install.

When the next nightly build you'd like to work with is posted, simply repeat the process placing the install into a folder of its own.

Stuart


 
 

________________________________________
From: Pedro Lino <pe...@gmail.com>
Sent: Thursday, June 12, 2014 2:08 PM
To: qa@openoffice.apache.org
Subject: Re: Using dailies under Windows

Hi Ouchka

msiexec / a openoffice400.msi.
>

This is essentially what I needed ;)

I still think it would be nice if the installer detected that the build is
newer and allowed to install without any "tricks". This would be more user
friendly ;)

Merci bien!

Kind regards,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: Using dailies under Windows

Posted by Pedro Lino <pe...@gmail.com>.
Hi Ouchka

msiexec / a openoffice400.msi.
>

This is essentially what I needed ;)

I still think it would be nice if the installer detected that the build is
newer and allowed to install without any "tricks". This would be more user
friendly ;)

Merci bien!

Kind regards,
Pedro

Re: Using dailies under Windows

Posted by Oukcha oukcha <ou...@gmail.com>.
Hi,

You can try (sorry, it’s automatic traduction fr -> en) :

1 - Once the exe file is downloaded, double-click unzip it, the following
steps take into account that the files are unpacked in a folder on the
desktop.

2 - Immediately after unpacking, abort the installation.
Windows Menu> All Programs> Accessories, right-click Command Prompt "> Run
as administrator.
(if the command prompt is not running as admin, installation error, even if
you are admin of your computer)

3 - When you see the prompt to start from the root, type this command :
cd \

4 - You must then go back to the desktop (desktop) of the user (Users)
profile concerned; each time you press the Tab key, the path is
automatically completed.
For example entering cd u followed by pressing Tab gives "cd Users".

5 - Once arrived at the AOO400 folder, type :
msiexec / a openoffice400.msi.

A old screenshot here :
http://cjoint.com/?DFmsMld2PNh

Regards