> > That isn't really a problem. Every package that uses shortcut.pl depends on
> > the activeperl package and every client that is installed with unattended
> > has activeperl installer already anyway.
> What do you use for ActivePerl?
Pretty much the same script as you posted (though, i'm still using build 1003
atm):
<packages>
<package id="activeperl" name="ActivePerl" revision="5.10.0.1003"
reboot="false">
<check type="logical" condition="and">
<check type="uninstall" condition="exists" path="ActivePerl 5.10.0 Build
1003" />
</check>
<install cmd='msiexec /qn /i
"%SOFTWARE_ISERV%\activeperl\activeperl-5.10.0.1003.msi" /norestart
PERL_PATH="Yes" PERL_EXT="YES"' />
<upgrade cmd='msiexec /qn /i
"%SOFTWARE_ISERV%\activeperl\activeperl-5.10.0.1003.msi" /norestart
PERL_PATH="Yes" PERL_EXT="YES"' />
<remove cmd='msiexec /qn /x
"%SOFTWARE_ISERV%\activeperl\activeperl-5.10.0.1003.msi" /norestart' />
<remove cmd='cmd /c IF EXIST "%SYSTEMDRIVE%\Perl" RMDIR "%SYSTEMDRIVE%\Perl"
/Q /S' />
</package>
</packages>
> Unfortunately it seems to fail if ActivePerl 5.8.8 is installed, as the MSI
> package seems to be unable to do upgrades :-(
Yeah, I've witnessed that problem with ActivePython. :/
But running the remove commands for "any" previous version that might be
installed and treating exitcode 1613 as successful should do the trick. ;) Its
really hacky but "works".
-
jens
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/wpkg-users
