Rainer Meier <r.meier at wpkg.org> writes: > Well, the Reply of David reminded me that I did not answer yet. > > So here it comes. > > For most applications I use a bunch of cmd scripts to install them. > First of all my generic installer ("install.cmd"). Then I use a simple > "unattended.cmd" batch file which makes use of "install.cmd". For > uninstall I am using a script called "unattended-uninstall.cmd". [...] > Other uninstall scripts might require invoking an uninstall EXE file > with specific parameters. My scripts take into account 32-bit and > 64-bit operating systems. Thanks everybody for your answers, looking at them I was wondering if having conditionnal variables could be a good thing, let me explain: I don't really like to have some external cmd scripts, it requires to look at multiple files to see what's happening with a package, what about something like this: ===== <?xml version='1.0' encoding='utf-8'?> <packages> <package id='7zip' name='7 Zip' revision='4.62' reboot='false' priority='100'> <check type='variable' name='PROCESSOR_ARCHITECTURE' condition='equals' value='x86'> <variable name='7zInstaller' value='7z462.msi'/> </check> <check type='variable' name='PROCESSOR_ARCHITECTURE' condition='equals' value='AMD64'> <variable name='7zInstaller' value='7z462-x64.msi'/> </check> <check type='uninstall' condition='exists' path='7-Zip 4.62'/> <install cmd='msiexec /qn /norestart /i %SOFTWARE%\zip\%7zInstaller%'/> <install cmd='regedit /s "%SOFTWARE%\zip\7zip.reg"'/> <upgrade cmd='msiexec /qn /norestart /i %SOFTWARE%\7zip\%7zInstaller%'/> <upgrade cmd='regedit /s "%SOFTWARE%\zip/7zip.reg"'/> <remove cmd='msiexec /qn /norestart /x %SOFTWARE%\zip\%7zInstaller%'/> </package> </packages> ===== Doing the same for the uninstall entry if it differ between x86 and x64 architectures. This would permit to have generic package definitions. Regards. -- Daniel Dehennin RAIP de l'Orne |