[mojosetup] Upgrade problems with MojoSetup

[Francois Gouget]

I'm running into a couple of problems when upgrading an application with 
MojoSetup.

So let's say that application was first installed into /opt/myapp' by 
the MojoSetup installer: running install-myapp-1.0.bin
This first installation created a bunch of files and directories, including:
    /opt/myapp/bin
    /opt/myapp/bin/oldfile

Then version 2.0 of myapp comes out and the user upgrades simply by 
running install-myapp-2.0.bin.


The first problem is that obsolete files don't get deleted. So even 
'oldfile' does not exist anymore in myapp 2.0, after going through the 
above '/opt/myapp/bin/oldfile' will still exist.


The second problem is that after running install-myapp-2.0.bin, 
MojoSetup has completely forgotten that it created '/opt/myapp/bin' when 
version 1.0 was installed. So when you next uninstall it does not delete 
the directories.


Both problems happen because the manifest created when 1.0 was installed 
is ignored and overwritten by the 2.0 install. Ignoring it means we 
don't know which files are no longer relevant and should be deleted. And 
it also means that since we don't put existing directories into the 
manifest, the new manifest does not list those created by 1.0, so that 
they don't get uninstalled either.

So I'm tempted to change that but I would like to know what other people 
think. Surely I'm not the first one to hit this problem?

Is the standard solution to force an uninstall of the old version before 
installing the new one? If so shouldn't MojoSetup complain before 
overwriting the old manifest?


-- 
François Gouget
fgouget at codeweavers.com