Opened 9 years ago

Closed 5 months ago

#1080 closed enhancement (wontfix)

Windows native installer: reinstall

Reported by: martinl Owned by: grass-dev@…
Priority: major Milestone: 6.4.6
Component: Installation Version: svn-releasebranch64
Keywords: wingrass Cc:
CPU: Unspecified Platform: MSWindows XP

Description

It would be useful to improve Windows native installer by adding reinstall method. Currently already installed GRASS is removed (including user settings) and afterwards installed the new version. It would be nice to add "reinstall" option when only modified (size-based or marked) files would be replaced. The user configuration should be untouched which is the key point.

Change History (5)

comment:1 in reply to:  description Changed 9 years ago by hellik

hi,

Replying to martinl:

It would be useful to improve Windows native installer by adding reinstall method. Currently already installed GRASS is removed (including user settings) and afterwards installed the new version. It would be nice to add "reinstall" option when only modified (size-based or marked) files would be replaced. The user configuration should be untouched which is the key point.

actual the wingrass-installer does following (see http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Installer.nsi#L160)

 	;.onInit Function (called when the installer is nearly finished initializing)
 	
 	;Check if GRASS is already installed on the system and, if yes, what version and binary release;
 	;depending on that, select the install procedure:
 	
 	;1. first installation = if GRASS is not already installed
 	;install GRASS asking for the install PATH
 	
 	;2. upgrade installation = if an older release of GRASS is already installed
 	;call the uninstaller of the currently installed GRASS release
 	;if the uninstall procedure succeeded, call the current installer without asking for the install PATH
 	;GRASS will be installed in the same PATH of the previous installation
 	
 	;3. downgrade installation = if a newer release of GRASS is already installed
 	;call the uninstaller of the currently installed GRASS release
 	;if the uninstall procedure succeeded, call the current installer without asking for the install PATH
 	;GRASS will be installed in the same PATH of the previous installation
 	
 	;4. repair installation = if the same release of GRASS is already installed
 	;call the uninstaller of the currently installed GRASS release
 	;if the uninstall procedure succeeded, call the current installer asking for the install PATH

so asked is rather an upgrade/update of the installation with a newer version and keeping the user configuration than a reinstall of several changed/newer files?

just replacing modified files (size-based or marked) could maybe problematic, if for example the underlying build system has changed with newer version of the dependecies?

best regards Helmut

comment:2 Changed 9 years ago by hellik

Milestone: 6.4.06.4.2

comment:3 Changed 6 years ago by hamish

I agree that trying to figure out a file-diff would be problematic. The current auto-uninstall the old ver & install from fresh the new ver isn't so bad if you aren't doing it every day.

the grassrc6 file is preserved for all but the msys startup (which has it's own /home/ somewhere other than the user's main one [is that safe for those with no write access to Program Files?])

Hamish

comment:4 Changed 3 years ago by neteler

Milestone: 6.4.26.4.6

comment:5 Changed 5 months ago by martinl

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.